On Tue, Nov 20, 2018 at 12:32 AM 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
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:
>
On Mon, Nov 19, 2018 at 3:13 PM Ruben Safir 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 ?
> >
> >
Hello,
It seems that some drivers in drivers/misc/eeprom does support write access.
For example at24.c seems to have a function at24_write().
https://github.com/torvalds/linux/blob/master/drivers/misc/eeprom/at24.c
However some drivers doesn’t have write support, I believe it is because of
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
>
> ___
>
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
