From: Lee Revell <rlrevell@joe-job.com>
To: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
Cc: Gene Heskett <gene.heskett@verizon.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [FC1], 2.6.8-rc2 kernel, new motherboard problems
Date: Sat, 24 Jul 2004 14:01:10 -0400 [thread overview]
Message-ID: <1090692070.845.9.camel@mindpipe> (raw)
In-Reply-To: <4102530C.8060604@gmx.net>
On Sat, 2004-07-24 at 08:16, Carl-Daniel Hailfinger wrote:
> Gene Heskett schrieb:
>
> > On Saturday 24 July 2004 02:06, Lee Revell wrote:
> >>>>Wow, nVidia won't release the specs for a *10/100 ethernet
> >>>>controller*? Having to reverse engineer a network driver is
> >>>>ridiculous in this day and age. I can understand binary-only
> >>>>graphics drivers, there is a lot of valuable IP in there, but
> >>>>this is a freaking network card. What do they expect people to
> >>>>do?
> >>>>
> >>>>Maybe some bad press would set them straight.
> >>>>
> >>>>Lee
>
> Could you please check the facts (or ask the driver authors) before
> suggesting to haunt NVidia with bad press? Thanks.
>
All the facts I needed to know were in the original post. You had to
reverse engineer a network driver because Nvidia would not release
specs. We should not be having to reverse engineer a 10/100 ethernet
controller in 2004. The Linux community should make noise when vendors
do this.
> > I'm under the impression the forcedeth writers did have access to this
> > data. Is this incorrect? The question is directed at the forcedeth
> > authors. If you are one, then please clarify.
>
> I am one of the authors. We did not have any information in the first
> place, but now that our reverse engineered driver works well, NVidia
> contributed bugfixes and gigabit support to our driver.
This is pretty shoddy on their part. Like I said, I can understand not
wanting to release the specs for their GFX cards, but a freaking 10/100
ethernet controller is ridiculous.
Lee
prev parent reply other threads:[~2004-07-24 18:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0407211334260.3000-100000@mail.birdvet.org>
[not found] ` <40FF4A15.7040100@charter.net>
[not found] ` <200407220652.39575.gene.heskett@verizon.net>
2004-07-22 12:49 ` [FC1], 2.6.8-rc2 kernel, new motherboard problems Gene Heskett
2004-07-22 18:49 ` Nuno Monteiro
2004-07-24 0:55 ` Lee Revell
2004-07-24 5:58 ` Gene Heskett
2004-07-24 6:06 ` Lee Revell
2004-07-24 6:10 ` Chris Wedgwood
2004-07-24 9:29 ` Gene Heskett
2004-07-24 9:20 ` Gene Heskett
2004-07-24 12:16 ` Carl-Daniel Hailfinger
2004-07-24 15:15 ` Gene Heskett
2004-07-24 18:01 ` Lee Revell [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=1090692070.845.9.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=c-d.hailfinger.kernel.2004@gmx.net \
--cc=gene.heskett@verizon.net \
--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