netdev - EEPROM infrastructure (was: [PATCH] eeprom

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200612151258.56213.netdev@axxeo.de>
Date:	Fri, 15 Dec 2006 12:58:55 +0100
From:	Ingo Oeser <netdev@...eo.de>
To:	Lennart Sorensen <lsorense@...lub.uwaterloo.ca>
Cc:	Ivo van Doorn <ivdoorn@...il.com>,
	"John W. Linville" <linville@...driver.com>,
	netdev@...r.kernel.org, Michael Wu <flamingice@...rmilk.net>,
	linux-kernel@...r.kernel.org, Ingo Oeser <ioe-lkml@...eria.de>
Subject: EEPROM infrastructure (was: [PATCH] eeprom_93cx6: Add write support)

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@...il.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
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html