From: Chriz Chow <cmcvista@gmail.com>
To: Ruben Safir <ruben@mrbrklyn.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Why eeprom driver is read-only ?
Date: Mon, 19 Nov 2018 21:48:13 +0800 [thread overview]
Message-ID: <C6280E40-2618-477C-897F-E76C9D2F9C68@gmail.com> (raw)
Message-ID: <20181119134813.nuDYODLdyBf446BHshWZFtNw-athyNXIUySgYua4UOE@z> (raw)
In-Reply-To: <aa10c4ab-6b08-3033-50db-a888a2d7ba81@mrbrklyn.com>
[-- Attachment #1.1: Type: text/plain, Size: 1737 bytes --]
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 simplicity - some eeprom are used for read only, such as ddr4 spd eeprom.
Point me out if I am wrong.
Chriz
Enviado desde mi iPhone
> El 19 nov 2018, a las 9:12 p. m., Ruben Safir <ruben@mrbrklyn.com> escribió:
>
>> 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?
>
>
> --
> 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
[-- Attachment #1.2: Type: text/html, Size: 3751 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2018-11-19 13:49 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 [this message]
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
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=C6280E40-2618-477C-897F-E76C9D2F9C68@gmail.com \
--to=cmcvista@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=ruben@mrbrklyn.com \
/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).