From: Jeff Garzik <jgarzik@pobox.com>
To: Cesar Eduardo Barros <cesarb@cesarb.net>
Cc: netdev@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] 2.6 driver for Silan SC92031
Date: Sat, 02 Dec 2006 17:27:51 -0500 [thread overview]
Message-ID: <4571FDE7.9060203@pobox.com> (raw)
In-Reply-To: <4571FC49.5060208@cesarb.net>
Cesar Eduardo Barros wrote:
> From: Cesar Eduardo Barros <cesarb@cesarb.net>
>
> This is a driver for the Silan SC92031/Rsltek 8139D NIC chip. It's a
> rewrite of the vendor 2.4 driver for 2.6, and has been lightly tested
> on a 2.6.17 x86-64 kernel with the Ubuntu patches (as a out-of-tree
> module only).
>
> This chip is found on at least one counterfeit Encore ENL832-TX-RENT
> NIC [1], which came with a mini-CD with the 2.4 driver. A slightly
> older version of the driver was found at [2]. The main difference
> between them is that the newer one has a small bugfix in the RX path,
> a lot of gratuitous renaming of functions, all the printable strings
> changed to show as a "Rsltek 8139D" [sic], and a PCI ID of 8139 instead
> of 2031.
>
> This patch has been modified to apply cleanly on 2.6.19; to run on
> 2.6.17, just add back the struct pt_regs* argument to the interrupt
> handler and to its call at poll_controller(). It compiles on 2.6.19 for
> x86-64 as a module.
>
> [1] See http://www.encore-usa.com/faq.php under ENL832-TX-RENT for more
> information
> [2] Look for SL_LINUX.ZIP (which is really a .tar.gz) at
> http://broadbandforum.in/dataone_Intex_LAN_cardlinux-t4207-s15.html
>
> Signed-off-by: Cesar Eduardo Barros <cesarb@cesarb.net>
Seems like it would be best to modify the existing 8139 driver...
Jeff
next prev parent reply other threads:[~2006-12-02 22:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-02 22:20 [PATCH] 2.6 driver for Silan SC92031 Cesar Eduardo Barros
2006-12-02 22:27 ` Jeff Garzik [this message]
2006-12-03 0:23 ` Cesar Eduardo Barros
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=4571FDE7.9060203@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@osdl.org \
--cc=cesarb@cesarb.net \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).