From: Chris Snook <csnook@redhat.com>
To: netdev@vger.kernel.org
Cc: synrg@debian.org
Subject: [RFC] introducing the Atheros L2 Fast Ethernet driver
Date: Tue, 04 Dec 2007 17:24:29 -0500 [thread overview]
Message-ID: <4755D39D.30005@redhat.com> (raw)
Hey folks --
I've begun cleaning up the atl2 vendor driver for merging. It's very similar
to the atl1 driver, and needs a lot of the same work, though I have already
fixed the 64-bit DMA data corrupter that atl1 users remember so fondly. Right
now this is very raw, and there is a large amount of cosmetic work to do to make
it more maintainable, but it should generally work, at least as well as the
vendor driver does.
While this is in pre-submission cleanup mode, the latest standalone source
tarball and patch (currently against 2.6.23) will be available here:
http://people.redhat.com/csnook/atl2/
If you have atl2 hardware, please give this a spin. I plan to submit the
driver for merging some time in the next month or so. Questions, comments,
patches welcome.
-- Chris
next reply other threads:[~2007-12-04 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 22:24 Chris Snook [this message]
2007-12-04 22:47 ` [RFC] introducing the Atheros L2 Fast Ethernet driver Jeff Garzik
2007-12-05 2:06 ` Chris Snook
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=4755D39D.30005@redhat.com \
--to=csnook@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=synrg@debian.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).