From: Vojtech Pavlik <vojtech@suse.cz>
To: Dave Jones <davej@codemonkey.org.uk>,
Alan <alan@lxorguk.ukuu.org.uk>,
"Matthew D. Pitts" <mpitts@suite224.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: NForce Chipset support in which kernels?
Date: Wed, 22 Jan 2003 22:12:37 +0100 [thread overview]
Message-ID: <20030122221237.A7122@ucw.cz> (raw)
In-Reply-To: <20030122013130.GA1652@codemonkey.org.uk>; from davej@codemonkey.org.uk on Wed, Jan 22, 2003 at 01:31:30AM +0000
On Wed, Jan 22, 2003 at 01:31:30AM +0000, Dave Jones wrote:
> On Tue, Jan 21, 2003 at 10:47:32PM +0000, Alan Cox wrote:
> > On Tue, 2003-01-21 at 15:24, Matthew D. Pitts wrote:
> > > Unless you get the drivers from nVIDIA website.
> >
> > Which are binary only. So its still best avoided
>
> For someone with far too much time on their hands, the
> 20KB binary object (complete with symbols) shouldn't be
> too much work to reverse engineer 8)
>
> Although Jeff seems to be think that the chip is a clone
> of another existing NIC, so it may not be worth the effort
> if $driver can be made to work with it by adding some IDs..
Well, the IDE part in nForce certainly is a clone of another IDE, so
it's likely the NIC is as well. An idea comes to mind which one it could
be ...
--
Vojtech Pavlik
SuSE Labs
next prev parent reply other threads:[~2003-01-22 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-17 21:11 NForce Chipset support in which kernels? Hanasaki JiJi
2003-01-20 8:54 ` Alan
2003-01-21 15:24 ` Matthew D. Pitts
2003-01-21 16:18 ` Jeff Garzik
2003-01-21 16:49 ` Matthew D. Pitts
2003-01-21 21:24 ` Bryan Andersen
2003-01-21 22:47 ` Alan
2003-01-22 1:31 ` Dave Jones
2003-01-22 21:12 ` Vojtech Pavlik [this message]
2003-01-22 21:25 ` Anders Gustafsson
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=20030122221237.A7122@ucw.cz \
--to=vojtech@suse.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davej@codemonkey.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mpitts@suite224.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox