public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric <eric@sage-aust.com.au>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvidia nforce 1.0-261 nvnet for kernel 2.5
Date: Tue, 29 Jul 2003 16:44:22 +0800	[thread overview]
Message-ID: <3F2633E6.3030205@sage-aust.com.au> (raw)

from various hardware source the NVNET hardware is probably this:

MCP integrated NVIDIA^R MAC + Realtek^R 8201BL PHY

The specs on asus and epox refer to using  the nvnet on the some fo 
their boards, in the detailed specs you get the above detail

Hope it helps
I could be persuaded to do some testing if required



             reply	other threads:[~2003-07-29  8:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-29  8:44 Eric [this message]
  -- strict thread matches above, loose matches on Subject: below --
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
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

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=3F2633E6.3030205@sage-aust.com.au \
    --to=eric@sage-aust.com.au \
    --cc=linux-kernel@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