From: Matti Aarnio <matti.aarnio@zmailer.org>
To: linux-kernel@vger.kernel.org
Subject: Re: OpenBSD driver for nforce-based ethernetcards.
Date: Mon, 13 Feb 2006 10:34:45 +0200 [thread overview]
Message-ID: <20060213083445.GX3927@mea-ext.zmailer.org> (raw)
In-Reply-To: <20060213082519.GN12484@boetes.org>
On Mon, Feb 13, 2006 at 09:24:56AM +0059, Han Boetes wrote:
> Date: Mon, 13 Feb 2006 09:24:56 +0059
> From: Han Boetes <han@mijncomputer.nl>
> To: linux-kernel@vger.kernel.org
> Subject: OpenBSD driver for nforce-based ethernetcards.
>
> Hi,
>
> I just read this announcement on a well known OpenBSD forum:
> http://undeadly.org/cgi?action=article&sid=20060206150238&mode=expanded
>
> So if anyone is interested in writing a driver for Linux for the
> nvidia ethernet cards: That's a nice place to start.
Quick browse of the forum:
Re: testers required for NVIDIA Ethernet driver (mod 2/4)
by Anonymous Coward (IP 208.252.48.163) on Mon Feb 6 21:31:33 2006 (GMT)
How much of this is based on the reverse engineered Linux driver for
forcedeth?
Re: testers required for NVIDIA Ethernet driver (mod 11/11)
by jsg (IP 210.15.216.215) on Mon Feb 6 22:39:51 2006 (GMT)
It was consulted for register offsets and semantics if we weren't sure
what was supposed to happen. If you look at the code you'll see our
driver is a hell of a lot easier on the eyes and like half the size.
So yes, perhaps 'forcedeth' driver would use some heavy handed
cleanup, but it does not mean it does not exist...
> The sourcecode can be found over here:
> http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/
> Under the name if_nfe*
>
> # Han
/Matti Aarnio
prev parent reply other threads:[~2006-02-13 8:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 8:25 Han Boetes
2006-02-13 8:34 ` Matti Aarnio [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=20060213083445.GX3927@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--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
all inboxes | Powered by JetHome®