> Subject: Re: [RFC PATCH V4 net-next 1/5] ethtool: Allow network drivers to > dump arbitrary EEPROM data > > > > +#define ETH_MODULE_EEPROM_PAGE_LEN 256 > > > > Sorry to keep raising issues, but I think you want to make this > > constant 128. > > Yes, i also think the KAPI should be limited to returning a maximum of a 1/2 > page per call. > > > > +#define MODULE_EEPROM_MAX_OFFSET (257 * > > > ETH_MODULE_EEPROM_PAGE_LEN) > > > > The device actually has 257 addressable chunks of 128 bytes each. > > With ETH_MODULE_EEPROM_PAGE_LEN set to 256, your constant is 2X too > big. > > > > Note also, SFP devices (but not QSFP or CMIS) actually have another > > 256 bytes available at 0x50, in addition to the full 257*128 at 0x51. > > So SFP is actually 259*128 or (256 + 257 * 128). > > > > Devices that don't support pages have much lower limits (256 bytes for > > QSFP/CMIS and 512 for SFP). Some SFP only support 256 bytes. Most > > devices will return nonsense for pages above 3. So, this check is > > really only an absolute limit. The SFP driver that takes this request > > will probably check against a more refined MAX length (eg modinfo- > >eeprom_len). > > > > I suggest setting this constant to 259 * (ETH_MODULE_EEPROM_PAGE_LEN > / 2). > > Let the driver refine it from there. > > I don't even see a need for this. The offset should be within one 1/2 page, of > one bank. So offset >= 0 and <= 127. Length is also > 0 and > <- 127. And offset+length is <= 127.
I like the clean approach, but... How do you request low memory? If all of the pages start at offset 0, then page 0 is at page 0, offset 0. That has always referred to low memory. (I have actually used 'page -1' for this in some code I don't share with others.) I believe all of this code currently is consistent with the paged area starting at offset 128. If that changes to start paged memory at offset 0, there are several places that will need to be adjusted. Whatever choice is made, there should be documentation scattered around in the code, man pages and Documentation directories to tell the user/programmer whether the paged area starts at offset 0 or offset 128. It is constantly confusing, and there is no obvious answer. > > For the moment, please forget about backwards compatibility with the IOCTL > interface. Lets get a new clean KAPI and a new clean internal API between > the ethtool core and the drivers. Once we have that agreed on, we can work > on the various compatibility shims we need to work between old and new > APIs in various places. > > Andrew Don
