Messages in this thread | | | Date | Wed, 7 Dec 2022 19:44:29 +0100 | From | Piergiorgio Beruto <> | Subject | Re: [PATCH v5 net-next 1/5] net/ethtool: add netlink interface for the PLCA RS |
| |
On Wed, Dec 07, 2022 at 06:48:03PM +0100, Andrew Lunn wrote: > > > And only return the actual version value, not the 0x0A. > > About this, at the moment I am reporting the 0x0A to allow in the future > > possible extensions of the standard. A single byte for the version may > > be too limited given this technology is relatively fresh. > > What you think of this? > > What does the standards document say about this 0x0A? It doesn't actually say much, except that it is the identifier for the OPEN Alliance mapping.
Excerpt:
" 4.1.1 IDM Constant field indicating that the address space is defined by this document. These bits shall read as 0x0A (Open Alliance).
4.1.2 VER Constant field indicating the version of this document the register map conforms to. Some registers/bits defined herein may not be available in all revisions. The management entity can read this register to provide backward compatibility. For the present revision of this specification, these bits shall read as indicated in Table A.1.0/Value. "
Thanks, Piergiorgio
| |