From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Linux-Kernel list <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@zip.com.au>,
"David S. Miller" <davem@redhat.com>
Subject: [BK PATCH] Merge e1000 gigabit driver (yay)
Date: Sat, 16 Feb 2002 05:08:18 -0500 [thread overview]
Message-ID: <3C6E2F92.FD196E71@mandrakesoft.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 714 bytes --]
Linus,
I'm pleased to submit to you a BK merge of Intel's e1000 driver. The
license is now "GPL or (BSD + patent grant)", which should satisfy those
concerns.
I would also like to publicly thank Intel for this work. The two
contributors listed have been very responsive to feedback, and they have
put a good deal of work into beating the driver into shape for a kernel
merge.
Now I just hope I can convince them to open up their hardware specs :)
Kind regards,
Jeff
--
Jeff Garzik | "Why is it that attractive girls like you
Building 1024 | always seem to have a boyfriend?"
MandrakeSoft | "Because I'm a nympho that owns a brewery?"
| - BBC TV show "Coupling"
[-- Attachment #2: net-drivers-2.5.txt --]
[-- Type: text/plain, Size: 1941 bytes --]
Pull from: http://gkernel.bkbits.net/net-drivers-2.5
(BK-only URL)
GNU patch: ftp://ftp.kernel.org/pub/linux/kernel/people/jgarzik/patches/2.5.5/e1000-4.2.4-k1.diff.bz2
---------------------------------------------------------------------------
ChangeSet@1.345, 2002-02-16 04:51:10-05:00, jgarzik@rum.normnet.org
Merge new gigabit ethernet driver e1000, from Intel.
Contributors: Christopher Leech @ Intel, Scott Feldman @ Intel
Documentation/networking/e1000.txt | 245 ++++
MAINTAINERS | 7
drivers/net/Config.help | 36
drivers/net/Config.in | 1
drivers/net/Makefile | 5
drivers/net/e1000/LICENSE | 69 +
drivers/net/e1000/Makefile | 16
drivers/net/e1000/e1000.h | 233 ++++
drivers/net/e1000/e1000_ethtool.c | 377 ++++++
drivers/net/e1000/e1000_mac.c | 1821 +++++++++++++++++++++++++++++++++
drivers/net/e1000/e1000_mac.h | 1383 +++++++++++++++++++++++++
drivers/net/e1000/e1000_main.c | 2036 +++++++++++++++++++++++++++++++++++++
drivers/net/e1000/e1000_osdep.h | 142 ++
drivers/net/e1000/e1000_param.c | 709 ++++++++++++
drivers/net/e1000/e1000_phy.c | 1485 ++++++++++++++++++++++++++
drivers/net/e1000/e1000_phy.h | 422 +++++++
drivers/net/e1000/e1000_proc.c | 760 +++++++++++++
17 files changed, 9747 insertions(+)
ChangeSet@1.333, 2002-02-14 03:25:36-05:00, jgarzik@rum.normnet.org
Add board id to via-rhine net driver, for board added in
previous revision (thus fixing the build).
drivers/net/via-rhine.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletion(-)
ChangeSet@?????, jgarzik@rum.normnet.org
Update 8139too net driver to new arg-free recalc_sigpending() API
function
drivers/net/8139too.c | 2 +-
1 files changed, 1 insertion(+), 1 deletion(-)
---------------------------------------------------------------------------
next reply other threads:[~2002-02-16 10:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-16 10:08 Jeff Garzik [this message]
2002-02-18 10:30 ` [BK PATCH] Merge e1000 gigabit driver (yay) Eric W. Biederman
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=3C6E2F92.FD196E71@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=akpm@zip.com.au \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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