netdev - Re: [PATCH 04/26] rt2x00: EEPROM 93Cx6

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: <20061213170520.GE26412@csclub.uwaterloo.ca>
Date:	Wed, 13 Dec 2006 12:05:20 -0500
From:	lsorense@...lub.uwaterloo.ca (Lennart Sorensen)
To:	Ivo van Doorn <ivdoorn@...il.com>
Cc:	Michael Wu <flamingice@...rmilk.net>,
	"John W. Linville" <linville@...driver.com>, netdev@...r.kernel.org
Subject: Re: [PATCH 04/26] rt2x00: EEPROM 93Cx6

On Wed, Dec 13, 2006 at 05:47:41PM +0100, Ivo van Doorn wrote:
> Do you need to actually write data to the eeprom chip?
> Currently the module does not support writing to the eeprom,
> this is something I could add (The original Ralink code, where this module
> is based on also contains the code to write to the EEPROM).

I am going to use it to write the custom pci vendor ID to the eeprom, so
yes I intend to write to it.  The code appears as if it has the ability
to write to the eeprom but I didn't look at all of it carefully yet.  I
don't actually have any need to read it back, although I intend to do so
to verify the contents.

--
Len Sorensen
-
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