> sysfs from userland. What were the appropriate method of accessing
> EEPROM from a network driver? AFAIK no functions were exported from
> eeprom.c.
Please state always which version you are using. There is code exactly
for your use case in the driver since ~2.6.30 (and clearly described as
such).
437 /*
438 * This lets other kernel code access the eeprom data. For example, it
439 * might hold a board's Ethernet address, or board-specific calibration
440 * data generated on the manufacturing floor.
441 */
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Attachment:
signature.asc
Description: Digital signature
