All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Michael Wu <flamingice@sourmilk.net>,
	"John W. Linville" <linville@tuxdriver.com>,
	netdev@vger.kernel.org
Subject: Re: [PATCH 04/26] rt2x00: EEPROM 93Cx6
Date: Wed, 13 Dec 2006 18:17:23 +0100	[thread overview]
Message-ID: <200612131817.23735.IvDoorn@gmail.com> (raw)
In-Reply-To: <20061213170520.GE26412@csclub.uwaterloo.ca>

On Wednesday 13 December 2006 18:05, Lennart Sorensen wrote:
> 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.

Currently the module does not contain any code to actually write to
the eeprom. I'll create a patch to add support for the writing.

      reply	other threads:[~2006-12-13 17:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-03 18:19 [PATCH 04/26] rt2x00: EEPROM 93Cx6 Ivo van Doorn
2006-12-03 18:39 ` Michael Wu
2006-12-03 18:45   ` Ivo van Doorn
2006-12-08 18:56   ` Ivo van Doorn
2006-12-09  2:00     ` Michael Wu
2006-12-09 13:05       ` Ivo Van Doorn
2006-12-13 15:44         ` Lennart Sorensen
2006-12-13 16:47           ` Ivo van Doorn
2006-12-13 17:05             ` Lennart Sorensen
2006-12-13 17:17               ` Ivo van Doorn [this message]

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=200612131817.23735.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=flamingice@sourmilk.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.