From: Jeff Garzik <jeff@garzik.org>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: netdev@vger.kernel.org
Subject: Re: Ethernet driver for SNI RM200/RM400 machines
Date: Tue, 08 May 2007 01:32:26 -0400 [thread overview]
Message-ID: <46400B6A.9040307@garzik.org> (raw)
In-Reply-To: <20070423220010.GA9541@alpha.franken.de>
Thomas Bogendoerfer wrote:
> I'm currently working on getting LINUX supported on SNI RM200/300/400
> machines (MIPS based servers and workstations). Most of the changes
> are already in Linus tree. What's now missing are some device drivers.
> One is an ethernet driver for the older EISA only RM200 and RM400
> machines. They are using an Intel 82596 ethernet chip. Currently
> there are 3 more or less different 82596 drivers in the tree, so
> I didn't want to add another modified copy. I took lasi_82596.c,
> extracted the common parts, put that in its own file and used
> that for lasi_82956.c and sni_82596.c. The patch is about 89k
> big, therefore I've placed it offline:
>
> http://www.alpha.franken.de/patches/sni_82596.diff
>
> The driver is tested on a HP B132 and a SNI RM400-220.
>
> I've already looked at 82596.c, which contains a 82596 driver for
> MVME boards. It's no big deal to use lib82596.c as well for
> that driver. Right now my VME gear is not usable for testing,
> so if anybody has hardware to test such a modified driver, please
> mail me.
>
> It would be great, if this driver could be included during the 2.6.22
> release cycle.
Email me the patch and I'll gladly review it... In general we want new
stuff to get some public exposure prior to upstream, though. That
usually means me merging into a branch that queues for release X+1,
while automatically propagating to akpm's -mm.
Jeff
prev parent reply other threads:[~2007-05-08 5:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-23 22:00 Ethernet driver for SNI RM200/RM400 machines Thomas Bogendoerfer
2007-05-08 5:32 ` Jeff Garzik [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=46400B6A.9040307@garzik.org \
--to=jeff@garzik.org \
--cc=netdev@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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;
as well as URLs for NNTP newsgroup(s).