PTP PMC example and system configuartion changes. (r8)
Updated a small change suggested by ron. Change-Id: I574cb950642ae6e96c0e888a7d358a7aa9aed944 Signed-off-by: Dinesh Neelapu <dinesh.neelapu@windriver.com>
This commit is contained in:
parent
bc2f3c07ed
commit
8fda6e80c1
@ -38,7 +38,7 @@ for it to start.
|
|||||||
designs have a single |PHC| shared between all the ports on the |NIC|, while
|
designs have a single |PHC| shared between all the ports on the |NIC|, while
|
||||||
others may have one |PHC| per port. Refer to the |NIC| documentation to
|
others may have one |PHC| per port. Refer to the |NIC| documentation to
|
||||||
determine if a |NIC| has multiple |PHCs|. Configuring a ``ptp4l`` instance
|
determine if a |NIC| has multiple |PHCs|. Configuring a ``ptp4l`` instance
|
||||||
with multiple interfaces, each with its own |PHC|, results in degraded
|
with multiple interfaces, each with its own |PHC| results in degraded
|
||||||
timing accuracy or other undesirable behaviors. This means that a given
|
timing accuracy or other undesirable behaviors. This means that a given
|
||||||
``ptp4l`` instance should only be configured with interfaces that are on the
|
``ptp4l`` instance should only be configured with interfaces that are on the
|
||||||
same |NIC| and share a |PHC|.
|
same |NIC| and share a |PHC|.
|
||||||
|
Loading…
Reference in New Issue
Block a user