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 17:47:41 +0100 [thread overview]
Message-ID: <200612131747.42035.IvDoorn@gmail.com> (raw)
In-Reply-To: <20061213154415.GA26415@csclub.uwaterloo.ca>
On Wednesday 13 December 2006 16:44, Lennart Sorensen wrote:
> On Sat, Dec 09, 2006 at 02:05:06PM +0100, Ivo Van Doorn wrote:
> > Nope, don't have that device. I'll create a patch that will place the eeprom
> > module in the /lib folder. I'll send that to the list as soon as possible.
>
> Hmm, I wonder if this will be of help for me trying to read/write a
> 93c46 connected to an exar uart (jsm driver). So far I was trying to
> bit bang the IO from user space through the PCI registers, but having a
> proper support in the driver would probably work better (so far I didn't
> get it to work although I haven't tried very hard yet).
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).
Ivo
next prev parent reply other threads:[~2006-12-13 16:47 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 [this message]
2006-12-13 17:05 ` Lennart Sorensen
2006-12-13 17:17 ` 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=200612131747.42035.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 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).