On Mon, Nov 19, 2018 at 3:13 PM Ruben Safir <ruben@xxxxxxxxxxxx> wrote: > > On 11/19/18 7:08 AM, Ranran wrote: > > Hello, > > > > What is the reason that kernel driver of eeprom is configured only as > > read-only ? > > > > Is it because the BIOS is stored there ? > > > > Is there a way to make it writable ? > > > > Thank you, > > Ran > > > > _______________________________________________ > > Kernelnewbies mailing list > > Kernelnewbies@xxxxxxxxxxxxxxxxx > > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies > > > > > because the ROM is read only? > That's interesting... I think the name is confusing, because this chips are also writable. Not only this, but in arm the eeprom (at24) is writable! But in the x86 I am using, it is readonly in kernel code: https://android.googlesource.com/kernel/omap/+/glass-omap-xrr02/drivers/misc/eeprom/eeprom.c static struct bin_attribute eeprom_attr = { .attr = { .name = "eeprom", .mode = S_IRUGO, }, .size = EEPROM_SIZE, .read = eeprom_read, }; Regards, ran > > -- > So many immigrant groups have swept through our town > that Brooklyn, like Atlantis, reaches mythological > proportions in the mind of the world - RI Safir 1998 > http://www.mrbrklyn.com > DRM is THEFT - We are the STAKEHOLDERS - RI Safir 2002 > > http://www.nylxs.com - Leadership Development in Free Software > http://www.brooklyn-living.com > > Being so tracked is for FARM ANIMALS and and extermination camps, > but incompatible with living as a free human being. -RI Safir 2013 > > _______________________________________________ > Kernelnewbies mailing list > Kernelnewbies@xxxxxxxxxxxxxxxxx > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies _______________________________________________ Kernelnewbies mailing list Kernelnewbies@xxxxxxxxxxxxxxxxx https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
