From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Oeser Subject: EEPROM infrastructure (was: [PATCH] eeprom_93cx6: Add write support) Date: Fri, 15 Dec 2006 12:58:55 +0100 Message-ID: <200612151258.56213.netdev@axxeo.de> References: <200612131956.51000.IvDoorn@gmail.com> <20061213190651.GF26412@csclub.uwaterloo.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Cc: Ivo van Doorn , "John W. Linville" , netdev@vger.kernel.org, Michael Wu , linux-kernel@vger.kernel.org, Ingo Oeser Return-path: Received: from mail.axxeo.de ([82.100.226.146]:36850 "EHLO mail.axxeo.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752053AbWLOMRF (ORCPT ); Fri, 15 Dec 2006 07:17:05 -0500 To: Lennart Sorensen In-Reply-To: <20061213190651.GF26412@csclub.uwaterloo.ca> Content-Disposition: inline Sender: netdev-owner@vger.kernel.org List-Id: netdev.vger.kernel.org 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 > > 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