Signed-off-by: Richard Cochran
---
phc2sys.c | 10 +-
ptp4l.c | 2 +-
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/phc2sys.c b/phc2sys.c
index 64bdf26..18d9a9c 100644
--- a/phc2sys.c
+++ b/phc2sys.c
@@ -1319,10 +1319,10 @@ static void usage(char *progname)
There is an industry wide effort underway to replace historically and
culturally loaded terms like master/slave with neutral alternatives.
The IEEE 1588 committee will most likely amend the standard, but so
far no consensus on the new terminology has been reached.
Most of the proposed alternative
On 8/18/20, Richard Cochran wrote:
> There is an industry wide effort underway to replace historically and
> culturally loaded terms like master/slave with neutral alternatives.
...
> The information flowing through a PTP network may best be described as
> a time signal. As any EE will tell you,
On 8/18/2020 1:43 PM, Richard Cochran wrote:
> There is an industry wide effort underway to replace historically and
> culturally loaded terms like master/slave with neutral alternatives.
> The IEEE 1588 committee will most likely amend the standard, but so
> far no consensus on the new terminol
On Tue, Aug 18, 2020 at 02:51:26PM -0700, Jacob Keller wrote:
> Yep, makes sense. Long term, after changing the stuff which doesn't
> impact config, we can work towards finding a way to deprecate and rename
> config options in a way that won't break existing deployment. I'm
> personally Ok with sim
Few suggestions:
AVB uses end-stations and relays, as well as initiator/responder as the
context maybe, like:
- PTP End Instance: The AVB talkers and listener end-stations. It may also
be a GM.
- PTP Relay Instance: Could be inside a bridge, a router, or a multiport
end-station.
- PTP .1AS in
