From: Jeff Garzik <jeff@garzik.org>
To: Auke Kok <auke-jan.h.kok@intel.com>
Cc: netdev@vger.kernel.org
Subject: Re: e1000: update device ID table for register dumps
Date: Fri, 09 Feb 2007 16:32:44 -0500 [thread overview]
Message-ID: <45CCE87C.9040106@garzik.org> (raw)
In-Reply-To: <20070119225313.297224186C@ahkok-mobl.jf.intel.com>
Auke Kok wrote:
> e1000: update device ID table for register dumps with new devices
>
> From: Auke Kok <auke-jan.h.kok@intel.com>
>
> The register dump routine of e1000 was missing several newer chipsets. I
> reimported the mac detection code from the linux e1000 driver. This fixes
> newer NIC's reporting that their bus type is PCI instead of PCI-e.
>
> Signed-off-by: Auke Kok <auke-jan.h.kok@intel.com>
> ---
>
> e1000.c | 154 ++++++++++++++++++++++++++++++++++++++++++---------------------
> 1 files changed, 103 insertions(+), 51 deletions(-)
applied
prev parent reply other threads:[~2007-02-09 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 22:53 e1000: update device ID table for register dumps Auke Kok
2007-01-19 23:20 ` e1000: update device ID table for register dumps [Is an *ethtool* patch] Auke Kok
2007-02-09 21:32 ` Jeff Garzik [this message]
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=45CCE87C.9040106@garzik.org \
--to=jeff@garzik.org \
--cc=auke-jan.h.kok@intel.com \
--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).