From: Jeff Garzik <jeff@garzik.org>
To: Daniel Drake <dsd@gentoo.org>
Cc: auke-jan.h.kok@intel.com, e1000-devel@lists.sourceforge.net,
netdev <netdev@vger.kernel.org>
Subject: Re: e1000 and ICH9 hardware
Date: Mon, 29 Oct 2007 10:45:38 -0400 [thread overview]
Message-ID: <4725F212.2030103@garzik.org> (raw)
In-Reply-To: <4725E125.4030103@gentoo.org>
Daniel Drake wrote:
> Are there any plans to add ICH9 support to the e1000 driver (I note
> there is a patch floating around), or is the intention that ICH9 users
> all move to e1000e?
They all should use e1000e.
Further, in 2.6.25 or so, some e1000 PCI IDs will be moved to e1000e,
and support removed in e1000.
e1000 is being frozen in time as "pre-PCI Express e1000's".
Jeff
next prev parent reply other threads:[~2007-10-29 14:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 13:33 e1000 and ICH9 hardware Daniel Drake
2007-10-29 14:45 ` Jeff Garzik [this message]
2007-10-29 16:01 ` David A. Ranch
2007-10-29 16:19 ` Kok, Auke
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=4725F212.2030103@garzik.org \
--to=jeff@garzik.org \
--cc=auke-jan.h.kok@intel.com \
--cc=dsd@gentoo.org \
--cc=e1000-devel@lists.sourceforge.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).