From: Rahul Karnik <rahul@genebrew.com>
To: Andrew de Quincey <adq_dvb@lidskialf.net>
Cc: Marcelo Penna Guerra <eu@marcelopenna.org>,
lkml <linux-kernel@vger.kernel.org>, Laurens <masterpe@xs4all.nl>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: [PATCH] nvidia nforce 1.0-261 nvnet for kernel 2.5
Date: Sun, 27 Jul 2003 10:01:50 -0400 [thread overview]
Message-ID: <3F23DB4E.1000203@genebrew.com> (raw)
In-Reply-To: <200307271301.41660.adq_dvb@lidskialf.net>
Andrew de Quincey wrote:
> I've just dumped the mmapped IO space on mine. The MAC address shows up at
> offset 0xa8, but the amd8111e driver is looking for it at 0x160 (there's just
> loads of 0x00 there).
Hmmmm, with this info I am able to get amd8111e to read the correct MAC
address, but the network connection does not seem to work anyway. How
would we know if this is the right driver anyway?
-Rahul
--
Rahul Karnik
rahul@genebrew.com
next prev parent reply other threads:[~2003-07-27 13:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-26 22:09 [PATCH] nvidia nforce 1.0-261 nvnet for kernel 2.5 Andrew de Quincey
2003-07-27 4:50 ` Rahul Karnik
2003-07-27 4:56 ` Rahul Karnik
2003-07-27 2:26 ` Marcelo Penna Guerra
2003-07-27 5:59 ` Rahul Karnik
2003-07-27 9:16 ` Laurens
2003-07-27 10:37 ` Rahul Karnik
2003-07-27 11:19 ` Andrew de Quincey
2003-07-27 11:22 ` Andrew de Quincey
2003-07-27 11:48 ` Rahul Karnik
2003-07-27 11:46 ` Andrew de Quincey
2003-07-27 12:02 ` Andrew de Quincey
2003-07-27 13:36 ` Rahul Karnik
2003-07-27 14:01 ` Rahul Karnik [this message]
2003-07-27 14:14 ` Andrew de Quincey
2003-07-27 14:44 ` Rahul Karnik
2003-07-27 15:46 ` Alan Cox
2003-07-27 16:28 ` Rahul Karnik
2003-07-27 19:51 ` Laurens
2003-07-28 1:09 ` Jeff Garzik
2003-07-27 23:11 ` Marcelo Penna Guerra
2003-07-28 8:53 ` Andrew de Quincey
2003-07-27 5:53 ` Brian Jackson
2003-07-29 8:44 Eric
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=3F23DB4E.1000203@genebrew.com \
--to=rahul@genebrew.com \
--cc=adq_dvb@lidskialf.net \
--cc=eu@marcelopenna.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masterpe@xs4all.nl \
/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).