From: Dave Jones <davej@suse.de>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Roy Sigurd Karlsbakk <roy@karlsbakk.net>, linux-kernel@vger.kernel.org
Subject: Re: nVidia NIC/IDE/something support?
Date: Sun, 19 May 2002 18:47:20 +0200 [thread overview]
Message-ID: <20020519184720.J15417@suse.de> (raw)
In-Reply-To: <200205191514.g4JFEsV13608@mail.pronto.tv> <E179T6e-0003x5-00@the-village.bc.nu>
On Sun, May 19, 2002 at 05:00:24PM +0100, Alan Cox wrote:
> > I just bought this Asus board, A7N266-VM, with nVidia IDE, LAN and god knows
> > chipset. Linux doesn't understand it, and I really want it... Any plans of
> > supporting this? See below for /proc/pci output.
>
> Depends if Nvidia want to be helpful. The audio is now supported (someone
> was able to deduce that it was a clone of the intel one). For the ethernet
> you might want to try random things that expect that much mmio and I/O
> space until you find what they licensed if its not their own
In 2.5 the amd74xx.c ide driver has an entry to support the nforce IDE
too, so it looks like quite a bit of the chipset could be variants of
existing components.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-05-19 16:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-19 15:14 nVidia NIC/IDE/something support? Roy Sigurd Karlsbakk
2002-05-19 15:58 ` Dave Jones
2002-05-19 16:23 ` Roy Sigurd Karlsbakk
2002-05-19 16:45 ` Alan Cox
2002-05-19 16:00 ` Alan Cox
2002-05-19 16:47 ` Dave Jones [this message]
2002-05-19 17:34 ` Alan Cox
2002-05-19 16:24 ` Michael Dunsky
2002-05-19 16:45 ` Alan Cox
2002-05-17 0:29 ` Pavel Machek
2002-05-22 6:05 ` fchabaud
2002-05-22 12:02 ` Pavel Machek
2002-05-22 13:15 ` Alan Cox
2002-05-22 17:11 ` fchabaud
-- strict thread matches above, loose matches on Subject: below --
2002-05-22 17:20 Hayden James
2002-05-22 18:05 ` Alan Cox
2002-05-22 22:22 ` Vojtech Pavlik
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=20020519184720.J15417@suse.de \
--to=davej@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
/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.