public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rahul Karnik <rahul@genebrew.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andrew de Quincey <adq_dvb@lidskialf.net>,
	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 12:28:07 -0400	[thread overview]
Message-ID: <3F23FD97.60207@genebrew.com> (raw)
In-Reply-To: <1059320761.13190.9.camel@dhcp22.swansea.linux.org.uk>

Alan Cox wrote:
> On Sul, 2003-07-27 at 15:44, Rahul Karnik wrote:
> 
>>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 

s/ethernet/IDE, oops.

>>that Nvidia would license a completely different ethernet chip, but who 
>>knows?
> 
> 
> AMD's older network component is the AMD PCnet32, which is a very
> different chip.

Yes we tried that as well, with no success. See:

http://marc.theaimsgroup.com/?l=linux-kernel&m=105831948827945&w=2

As far as I can tell, NForce is based on AMD8111, at least for IDE and 
sound. Unfortunately, ethernet is a no-go so far with amd8111e.

Thanks,
Rahul
-- 
Rahul Karnik
rahul@genebrew.com


  reply	other threads:[~2003-07-27 15:56 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
2003-07-27 15:46                   ` Alan Cox
2003-07-27 16:28                     ` Rahul Karnik [this message]
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=3F23FD97.60207@genebrew.com \
    --to=rahul@genebrew.com \
    --cc=adq_dvb@lidskialf.net \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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