From: Jeff Garzik <jgarzik@pobox.com>
To: "Feldman, Scott" <scott.feldman@intel.com>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com,
LOSTeam <losteam@intel.com>
Subject: Re: [ANNOUNCE] Intel PRO/100 software developer manual released
Date: Tue, 17 Dec 2002 17:59:59 -0500 [thread overview]
Message-ID: <3DFFAC6F.9010903@pobox.com> (raw)
In-Reply-To: <288F9BF66CD9D5118DF400508B68C44604758F6C@orsmsx113.jf.intel.com>
Feldman, Scott wrote:
> Available at https://sourceforge.net/projects/e1000.
>
> The full title is:
>
> Intel 8255x 10/100 Mbps Ethernet Controller Family
> Open Source Software Developer Manual
> Revision 1.0
>
> The manual is intended to support the maintenance of the e100 driver (or the
> best driver for the PRO/100 networking hardware ;-). The manual covers the
> 82557, 82558, 82559, 82550, and 82551 Ethernet controllers.
>
> I would like to thank Jeff Garzik for encouraging this publication, and for
> having the patience to deal with the Intel machine.
I'm surprised that this David (me) actually got through to the Goliath :)
Let me publicly thank Intel NIC team [and related persons] for some
great work. You guys have really been responsive both to technical
issues and also political/community-related issues like this one of
opening docs.
This is a situation where I really think that opening docs will lead to
a better overall user experience with Intel hardware on Linux, and
hopefully serves as a model for other vendors to follow.
Thanks and kudos, Intel!
Jeff
next prev parent reply other threads:[~2002-12-17 22:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-17 22:03 [ANNOUNCE] Intel PRO/100 software developer manual released Feldman, Scott
2002-12-17 22:59 ` Jeff Garzik [this message]
2002-12-18 3:27 ` Anton Blanchard
2002-12-18 6:34 ` Greg KH
2002-12-18 8:34 ` James Morris
-- strict thread matches above, loose matches on Subject: below --
2002-12-18 3:46 Feldman, Scott
2002-12-18 17:07 Feldman, Scott
2002-12-18 22:41 Feldman, Scott
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=3DFFAC6F.9010903@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=losteam@intel.com \
--cc=netdev@oss.sgi.com \
--cc=scott.feldman@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.