From: Ranran <ranshalit@gmail.com>
To: Valdis Kletnieks <valdis.kletnieks@vt.edu>
Cc: ruben@mrbrklyn.com, kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: Why eeprom driver is read-only ?
Date: Tue, 20 Nov 2018 08:44:50 +0200 [thread overview]
Message-ID: <CAJ2oMhL-cx8==aBZdkS8RaP3L-45WN=mEsiyt2LFg=fx_S2zNA@mail.gmail.com> (raw)
Message-ID: <20181120064450.7WT3lC17vMkzC9mAeNZk_YvNuuB27v9gsUc7p-SET2s@z> (raw)
In-Reply-To: <177621.1542666723@turing-police.cc.vt.edu>
On Tue, Nov 20, 2018 at 12:32 AM <valdis.kletnieks@vt.edu> wrote:
>
> On Tue, 20 Nov 2018 00:04:03 +0200, Ranran said:
>
> > 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,
> > };
>
> Well, at least in the mainline kernel, we have this at the top of the eeprom.c file:
>
> /* Addresses to scan */
> static const unsigned short normal_i2c[] = { 0x50, 0x51, 0x52, 0x53, 0x54,
> 0x55, 0x56, 0x57, I2C_CLIENT_END };
>
>
> /* Size of EEPROM in bytes */
> #define EEPROM_SIZE 256
>
> which is pretty obviously intended for "very small eeprom hanging off an I2C adapter",
> and thus probably *NOT* the boot ROM that the BIOS lives in.
although I think that in my system it is a flash rom which stores the
BIOS, so I really don't know what's the use of the eeprom....
I need a very small amout of data (several bytes) to save some non
volatile information in x86 system.
I can't use disk for this, but can use any other peripheral or even
x86 chip on board.
Now it also seems that I can't use the eeprom becuase of the kernel
limitation (can I open it for writing if the BIOS is not stored
there??)
I don't have any idea where I can find such storage.
Does x86 include some programmable registers ?
Do you have any idea where I can store the data ?
Thanks
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2018-11-20 6:45 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
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 [this message]
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='CAJ2oMhL-cx8==aBZdkS8RaP3L-45WN=mEsiyt2LFg=fx_S2zNA@mail.gmail.com' \
--to=ranshalit@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=ruben@mrbrklyn.com \
--cc=valdis.kletnieks@vt.edu \
/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: link
Be 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).