Hello Richard,
at least for me the specification is quite confusing at this point.
Chapter "10.5.4.1 General Signaling message specifications" of IEEE8021AS-2011
describes
targetPortIdentity with a size of 10 octets.
But the following chapter mentions only 0xFF and not 0xFF FFFF FFFF FFFF FFFF.
> 10.5.4.2 Signaling message field specifications
> 10.5.4.2.1 targetPortIdentity
(PortIdentity)
> The value is 0xFF.
--
Mit freundlichen Grüßen / Best regards
Timo Wischer
Cross-Domain Computing Solutions
Engineering Architecture and Core Functions PSA and GM projects (XC-CI1/EPC1-E)
Robert Bosch Car Multimedia GmbH | Postfach | 31132 Hildesheim | GERMANY |
www.bosch.com
Tel. +49(5121)49-2672 | Fax +49(5121)49-6999 | timo.wisc...@de.bosch.com
Registered Office: Hildesheim, Registration Court: Amtsgericht Hildesheim HRB
201334
Chairman of the Supervisory Board: Dr. Walter Schirm; Managing Directors: Dirk
Biermann; Andree
Zahir
On Wed, 2021-03-10 at 06:59 -0800, Richard Cochran wrote:
> On Wed, Mar 10, 2021 at 09:47:18AM +0100, Timo Wischer via Linuxptp-devel
> wrote:
> > +const struct PortIdentity wildcard_pid2 = {
> > + .clockIdentity = {
> > + {0xff, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00}
> > + },
> > + .portNumber = 0x0000,
>
> Where does this wildcard come from?
>
> (I don't recall seeing it in 802.1AS)
>
> Thanks,
> Richard
_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
