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:44:08 -0400 [thread overview]
Message-ID: <3F23E538.6010900@genebrew.com> (raw)
In-Reply-To: <200307271514.00724.adq_dvb@lidskialf.net>
Andrew de Quincey wrote:
> Hmm, I have a suspicion it is not unfortunately, given the change in location
> of the MAC address. Or maybe nvidia have displaced the configuration
> registers by some amount?
Dunno. Look in the list archives for earlier discussions on the topic.
It seems AMD audio is a clone of Intel audio, which is why Intel audio
works for NForce. Since both audio and ethernet match, it seems unlikely
that Nvidia would license a completely different ethernet chip, but who
knows?
Anyway, I want to put as much info out there as possible for someone to
use as they wish. So here's another tip:
00:04.0 Ethernet controller: nVidia Corporation nForce2 Ethernet
Controller (rev a1)
00: de 10 66 00 07 00 b0 00 a1 00 00 02 00 00 00 00
10: 00 00 00 e0 01 c4 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 62 14 0c 57
30: 00 00 00 00 44 00 00 00 00 00 00 00 0b 01 01 14
40: 62 14 0c 57 01 00 02 fe 00 01 00 00 04 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Note the first row reads:
00: de 10 66 00 07 00 b0 00 a1 00 00 02 00 00 00 00
Before nvnet loads, the same row reads:
00: de 10 66 00 03 00 b0 00 a1 00 00 02 00 00 00 00
Don't know if that is significant.
-Rahul
--
Rahul Karnik
rahul@genebrew.com
next prev parent reply other threads:[~2003-07-27 14:12 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
2003-07-27 14:14 ` Andrew de Quincey
2003-07-27 14:44 ` Rahul Karnik [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=3F23E538.6010900@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 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.