On Tue, Jan 24, 2012 at 12:13 PM, Wolfram Sang <w.sang@xxxxxxxxxxxxxx> wrote: >> 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? > > I haven't used it myself, but using LXR [1] you can check current users > of at24_platform_data and find users (davinci) using this feature. > > [1] http://lxr.linux.no/#linux+v3.2.1/include/linux/i2c/at24.h Thanks. It's working now. I was lucky to have DaVinci based EMAC in am3517, so I only had to adjust the code on the platform side. The driver itself was left untouched. For USB based NIC and WLAN I'll need to get my hands on their drivers :-( I submitted a patch to eeprom's documentation. At this point I have a question? Are those TODO items still valid? At least in regards of write capability? In 2.6.37 kernel I can write to EEPROM through sysfs entry. Unfortunately I can't test any 3.x kernel because PSP for am3517 is still not finished. 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
