From: apgo@patchbomb.org (Arthur Othieno)
To: Lee Revell <rlrevell@joe-job.com>
Cc: Adrian Bunk <bunk@stusta.de>,
jgarzik@pobox.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] CONFIG_FORCEDETH updates
Date: Mon, 13 Feb 2006 03:36:35 -0500 [thread overview]
Message-ID: <20060213083635.GD14516@krypton> (raw)
In-Reply-To: <1139781817.19342.300.camel@mindpipe>
On Sun, Feb 12, 2006 at 05:03:36PM -0500, Lee Revell wrote:
> On Sun, 2006-02-12 at 18:52 +0100, Adrian Bunk wrote:
> > This patch contains the following possible updates:
> > - let FORCEDETH no longer depend on EXPERIMENTAL
> > - remove the "Reverse Engineered" from the option text:
> > for the user it's important which hardware the driver supports, not
> > how it was developed
>
> Is this driver as stable as one that was developed with proper
> documentation?
Been using it on nForce since v0.19 (circa 2003) with no problems.
I doubt there are that many (significant) users of the binary driver
left..
And like Alistair pointed out:
drivers/net/forcedeth:17: * Copyright (c) 2004 NVIDIA Corporation
> I prefer to know that something as elementary as a fast ethernet
> controller had to be reverse engineered so I can avoid supporting
> a vendor so hostile to Linux.
Then how about moving the "Reverse Engineered" to the help text instead?
prev parent reply other threads:[~2006-02-13 8:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-12 17:52 [RFC: 2.6 patch] CONFIG_FORCEDETH updates Adrian Bunk
2006-02-12 22:03 ` Lee Revell
2006-02-12 22:47 ` Alistair John Strachan
2006-02-13 8:36 ` Arthur Othieno [this message]
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=20060213083635.GD14516@krypton \
--to=apgo@patchbomb.org \
--cc=bunk@stusta.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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.