From: Carl-Daniel Hailfinger <c-d.hailfinger.kernel.2004@gmx.net>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: linux-kernel@vger.kernel.org, Lee Revell <rlrevell@joe-job.com>
Subject: Re: [FC1], 2.6.8-rc2 kernel, new motherboard problems
Date: Sat, 24 Jul 2004 14:16:12 +0200 [thread overview]
Message-ID: <4102530C.8060604@gmx.net> (raw)
In-Reply-To: <200407240520.31906.gene.heskett@verizon.net>
Gene Heskett schrieb:
> On Saturday 24 July 2004 02:06, Lee Revell wrote:
>
>>On Sat, 2004-07-24 at 01:58, Gene Heskett wrote:
>>
>>>On Friday 23 July 2004 20:55, Lee Revell wrote:
>>>
>>>>On Thu, 2004-07-22 at 14:49, Nuno Monteiro wrote:
>>>>
>>>>>On 2004.07.22 13:49, Gene Heskett wrote:
>>>>>
>>>>>>00:04.0 Ethernet controller: nVidia Corporation nForce2
>>>>>>Ethernet Controller (rev a1)
>>>>>> Subsystem: Biostar Microtech Int'l Corp: Unknown
>>>>>>device 2301
>>>>>>
>>>>>>However, this, nor the xconfig helps, still don't indicate
>>>>>>which driver I should be using, or where to get it if its not
>>>>>>in the kernel's tree yet a/o 2.6.8-rc2. So thats the next
>>>>>>piece of data I need.
>>>>>
>>>>>Hi Gene,
>>>>>
>>>>>
>>>>>I believe you'll need forcedeth.c for this one. It's called
>>>>>"Reverse Engineered nForce Ethernet support", under Device
>>>>>Driver -> Networking -> Ethernet 10/100 Mbit.
Right. And it should work perfectly with that driver. However, I recommend
to use at least 2.6.8-rc2 because it has some bugfixes you may need.
>>>>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.
>>>Nvidia is immune to bad press, and probably cannot release a thing
>>>other than some API help due to copyright contracts with the
>>>coders who wrote their winderz drivers for them, The only cure
>>>would be for them to hired a couple of dozen programmers of the
>>>minimum quality the open source programmers exhibit, which I
>>>happen to think is top notch, and the CEO can only see outgo
>>>without compensatory income for all that salary, so they contract
>>>it out for a known cost, and get tied up in restrictive contracts.
>>
>>I am not talking about them releasing driver code, I am just talking
>>about datasheets so we can write our own driver, something that
>>tells you which bits to write to which registers to get it to do
>>$FOO.
>>
>>Their net cost: $0.
>>
>>Lee
>
>
> 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.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
next prev parent reply other threads:[~2004-07-24 12:16 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 [this message]
2004-07-24 15:15 ` Gene Heskett
2004-07-24 18:01 ` Lee Revell
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=4102530C.8060604@gmx.net \
--to=c-d.hailfinger.kernel.2004@gmx.net \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox