> > > The eeprom tested is from ST, model M24C64. Should this be added in the code > > > or in some doc folder? > > I think FIXMEs should be in the source itself. > > Do you want this as a patch of its own, or as an update of the old patch? Incremental please. Your other patch is already applied in my for-next branch :) > > Well, the "24c02ro" version will solve our use-case and is by far the > simplest to implement. But as you say it does not scale well with more > features. I can however not see any practical use-cases where we would need > anything else (like "write-only" for instance). I can make an implementation > of that so you can see how it looks. And most likely, this could be combined > with a DT/sysfs version to do the same without breaking anything in the > future if that is required. Yes, go ahead and let's have a look. I am quite positive I will like it. > One more question, I'm thinking about trying to use the "request_firmware()" > in the kernel in some way to be able to automatically populate the eeprom > with content from some file (the equivalent of a "pre-flashed eeprom"). Do > you have any thoughts about adding a feature like that? I see. Sounds reasonable, yet I need to think about it more.
Attachment:
signature.asc
Description: PGP signature
