On Tue, Jan 24, 2012 at 11:13 AM, Yegor Yefremov <yegorslists@xxxxxxxxxxxxxx> wrote: > On Tue, Jan 24, 2012 at 11:06 AM, Wolfram Sang <w.sang@xxxxxxxxxxxxxx> wrote: >> >>> 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 */ > > Thanks. My bad, I overlooked this. Wolfram, do you have any example how to access at24_macc_read()? My kernel is 2.6.37. Theres is a statement to export this code to the kernel via chip.setup(), which appears to be NULL. What headers do I need in the network driver? Regards, Yegor -- To unsubscribe from this list: send the line "unsubscribe linux-i2c" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
