Re: [Linuxptp-users] List of Boundary clocks
PTP IEEE 1588 stack for Linux
Brought to you by:
rcochran
From: Mozhdeh K. <kam...@gm...> - 2013-04-18 17:01:18
|
Thank you so much for your answers. So, by having a real BC, and those NICS (such as Intel's 82576 chip or Intel 82574 ) with linuxptp can I emulate the network? It is written in linuxptp readme that it implements the boundary clock, is it means by having a real BC and connect it to the linux which has linuxptp, it will recognize it and can be a slave for it? Mozhdeh On Mon, Apr 15, 2013 at 6:17 PM, Richard Cochran <ric...@gm...>wrote: > On Sun, Apr 14, 2013 at 04:33:36PM +0200, Mozhdeh Kamel wrote: > > I am totally getting confused regarding the hardware you introduced me. > As > > what I found, these are reference design board.. I confused how I can use > > those. > > Your question was... > > On Sun, Apr 14, 2013 at 02:35:11PM +0200, Mozhdeh Kamel wrote: > > Can you please tell me the list of hardware which support both HW > > timestamps and boundary clocks? > > and the answer is that, as far as I know, only the Freescale boards > will work "out of the box" as a BC, with the Linux kernel and the > linuxptp stack. For example, the P2020RBD has three Ethernet ports. > It is a complete embedded computer, and so you could run ptp4l on the > three ports as a BC. > > > I think you have read my scenario for testing IEEE1588 (bu using virtual > > machines and NIC). Before that, I thought I can have a proper network > > interface card that support hardware timestamps and use linuxptp .. > then I > > can have boundary clock and ordinary clock and etc .. Is it wrong? But > with > > what you introduce.. I don't know how I can use it. > > The important point is that a BC must have _two_or_more_ ports. > Just having one PCI card with HW time stamps is not enough. The BC > must have multiple ports all sharing the same clock. > > If I understood your project idea, you are interested in the effects > of using PTP over BCs in a WAN, and you want to simulate different > kinds of network delay and jitter. In this case, I would recommend > just using a commercial BC. Getting you own home made BC working is a > whole project in itself. > > HTH, > Richard > |