From: Jeff Garzik <jeff@garzik.org>
To: akpm@osdl.org
Cc: netdev@vger.kernel.org, cesarb@cesarb.net
Subject: Re: [patch 3/7] driver for Silan SC92031 netdev
Date: Tue, 26 Dec 2006 16:42:29 -0500 [thread overview]
Message-ID: <45919745.4080106@garzik.org> (raw)
In-Reply-To: <200612192108.kBJL8l4u010493@shell0.pdx.osdl.net>
akpm@osdl.org wrote:
> From: Cesar Eduardo Barros <cesarb@cesarb.net>
>
> This is a driver for the Silan SC92031/Rsltek 8139D NIC chip.
>
> 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. The
> driver on this patch is a rewrite of the vendor drivers (based mostly on
> the older one).
>
> Changes from the previous patch sent to netdev:
> - Use MMIO instead of PIO
> - Changed TX bounce buffers allocation
> - Use skb_copy_and_csum_dev
> - Several small bug fixes
> - Tested for more than just a few minutes each time
>
> [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
> [3] To compile on 2.6.17, simply add back the last argument to the
> interrupt handler in two places, and copy the boolean declarations
> from 2.6.19
>
> [akpm@osdl.org: build fixes]
> Signed-off-by: Cesar Eduardo Barros <cesarb@cesarb.net>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
applied
prev parent reply other threads:[~2006-12-26 21:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 21:08 [patch 3/7] driver for Silan SC92031 netdev akpm
2006-12-26 21:42 ` 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=45919745.4080106@garzik.org \
--to=jeff@garzik.org \
--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).