From: Daniel Drake <dsd@gentoo.org>
To: auke-jan.h.kok@intel.com
Cc: e1000-devel@lists.sourceforge.net, netdev <netdev@vger.kernel.org>
Subject: e1000 and ICH9 hardware
Date: Mon, 29 Oct 2007 13:33:25 +0000 [thread overview]
Message-ID: <4725E125.4030103@gentoo.org> (raw)
Hi,
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?
Just wondering which approach to take in terms of getting this hardware
supported in Gentoo's 2.6.23 kernels.
Thanks!
Daniel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
next reply other threads:[~2007-10-29 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 13:33 Daniel Drake [this message]
2007-10-29 14:45 ` e1000 and ICH9 hardware Jeff Garzik
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=4725E125.4030103@gentoo.org \
--to=dsd@gentoo.org \
--cc=auke-jan.h.kok@intel.com \
--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).