From: Ingo Oeser <netdev@axxeo.de>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Ivo van Doorn <ivdoorn@gmail.com>,
"John W. Linville" <linville@tuxdriver.com>,
netdev@vger.kernel.org, Michael Wu <flamingice@sourmilk.net>,
linux-kernel@vger.kernel.org, Ingo Oeser <ioe-lkml@rameria.de>
Subject: EEPROM infrastructure (was: [PATCH] eeprom_93cx6: Add write support)
Date: Fri, 15 Dec 2006 12:58:55 +0100 [thread overview]
Message-ID: <200612151258.56213.netdev@axxeo.de> (raw)
In-Reply-To: <20061213190651.GF26412@csclub.uwaterloo.ca>
Lennart Sorensen schrieb:
> On Wed, Dec 13, 2006 at 07:56:50PM +0100, Ivo van Doorn wrote:
> > This patch addes support for writing to the eeprom,
> > this also moves some duplicate code into seperate functions.
> >
> > Signed-off-by Ivo van Doorn <IvDoorn@gmail.com>
>
> Thank you. I will have a try with that to see if I can get that to work
> with the jsm driver. Too bad the serial drivers don't have any
> geteeprom/seteeprom standard ioctl's the way ethtool does for network
> devices.
It might be even better to have eeprom writing infrastructure.
Many device types come with eeproms today and they implement
it per driver or subsystem. On embedded platforms these EEPROMs
might even be shared among different devices.
So it might be time to generalize this like we did with LEDs.
Any comments?
Regards
Ingo Oeser
next prev parent reply other threads:[~2006-12-15 12:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-13 18:56 [PATCH] eeprom_93cx6: Add write support Ivo van Doorn
2006-12-13 19:06 ` Lennart Sorensen
2006-12-15 11:58 ` Ingo Oeser [this message]
2006-12-21 7:22 ` Ivo Van Doorn
2006-12-21 18:54 ` Ivo van Doorn
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=200612151258.56213.netdev@axxeo.de \
--to=netdev@axxeo.de \
--cc=flamingice@sourmilk.net \
--cc=ioe-lkml@rameria.de \
--cc=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=netdev@vger.kernel.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: 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).