From: ranshalit@gmail.com (Ranran) To: kernelnewbies@lists.kernelnewbies.org Subject: Why eeprom driver is read-only ? Date: Tue, 20 Nov 2018 00:04:03 +0200 [thread overview] Message-ID: <CAJ2oMhLXRqM6xR_FXD6ckX5D3m7iz2oeSd8B2qvZj8ka+oHMSA@mail.gmail.com> (raw) In-Reply-To: <aa10c4ab-6b08-3033-50db-a888a2d7ba81@mrbrklyn.com> On Mon, Nov 19, 2018 at 3:13 PM Ruben Safir <ruben@mrbrklyn.com> 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 at kernelnewbies.org > > 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 at kernelnewbies.org > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
WARNING: multiple messages have this Message-ID (diff)
From: Ranran <ranshalit@gmail.com> To: ruben@mrbrklyn.com Cc: kernelnewbies <kernelnewbies@kernelnewbies.org> Subject: Re: Why eeprom driver is read-only ? Date: Tue, 20 Nov 2018 00:04:03 +0200 [thread overview] Message-ID: <CAJ2oMhLXRqM6xR_FXD6ckX5D3m7iz2oeSd8B2qvZj8ka+oHMSA@mail.gmail.com> (raw) Message-ID: <20181119220403.cAAD5XF7mpXdlVRJUVmeXX0n1Hv21gzUOGX7kyDlVu4@z> (raw) In-Reply-To: <aa10c4ab-6b08-3033-50db-a888a2d7ba81@mrbrklyn.com> On Mon, Nov 19, 2018 at 3:13 PM Ruben Safir <ruben@mrbrklyn.com> 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@kernelnewbies.org > > 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@kernelnewbies.org > https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2018-11-19 22:04 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-11-19 12:08 Why eeprom driver is read-only ? Ranran 2018-11-19 12:08 ` Ranran 2018-11-19 13:12 ` Ruben Safir 2018-11-19 13:12 ` Ruben Safir 2018-11-19 13:48 ` Chriz Chow 2018-11-19 13:48 ` Chriz Chow 2018-11-19 22:04 ` Ranran [this message] 2018-11-19 22:04 ` Ranran 2018-11-19 22:32 ` valdis.kletnieks at vt.edu 2018-11-19 22:32 ` valdis.kletnieks 2018-11-20 6:44 ` Ranran 2018-11-20 6:44 ` Ranran 2018-11-19 14:07 ` valdis.kletnieks at vt.edu 2018-11-19 14:07 ` valdis.kletnieks
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAJ2oMhLXRqM6xR_FXD6ckX5D3m7iz2oeSd8B2qvZj8ka+oHMSA@mail.gmail.com \ --to=ranshalit@gmail.com \ --cc=kernelnewbies@lists.kernelnewbies.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).