From: Jon Mason <jdmason@us.ibm.com>
To: "cramerj" <cramerj@intel.com>
Cc: "Ben Greear" <greearb@candelatech.com>,
"Ganesh Venkatesan" <ganesh.venkatesan@gmail.com>,
netdev@oss.sgi.com
Subject: Re: ethtool -d no longer works for e1000
Date: Wed, 9 Mar 2005 18:54:34 -0600 [thread overview]
Message-ID: <200503091854.34466.jdmason@us.ibm.com> (raw)
In-Reply-To: <76FA8CF8F1F53240BB5B962A3385A5800256F787@orsmsx405>
On Wednesday 09 March 2005 06:35 pm, cramerj wrote:
> Ah! Yes, if you're running ethtool 1.8, then this was an issue (or
> rather, an annoyance) in e1000.c where we would default to mac_type =
> e1000_undefined for any newer hardware. Continuous updates to this file
> for every piece of hardware we released got old pretty quick. We've
> since changed the default mac_type to e1000_82543, which has a basic set
> of registers that haven't changed with each hardware release. And
> although the e1000_82546 mac_type exists, it isn't yet being assigned to
> the 82546GB hardware (again, see e1000.c), thus the error.
>
> Long story short, an updated ethtool should do the trick.
>
> Thanks,
> -Jeb
Ah, I am running ethtool 3 on a 82545 chip, that is probably why mine works.
Thanks,
Jon
next prev parent reply other threads:[~2005-03-10 0:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 0:35 ethtool -d no longer works for e1000 cramerj
2005-03-10 0:54 ` Jon Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-09 22:25 cramerj
2005-03-09 23:02 ` Ben Greear
2005-03-09 21:35 Ben Greear
2005-03-09 22:09 ` Ganesh Venkatesan
2005-03-09 23:09 ` Ben Greear
2005-03-09 23:13 ` Jon Mason
2005-03-09 23:31 ` Ben Greear
2005-03-09 23:42 ` Ben Greear
2005-03-11 8:54 ` Lennert Buytenhek
2005-03-11 8:55 ` Lennert Buytenhek
2005-03-09 22:59 ` Andre Tomt
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=200503091854.34466.jdmason@us.ibm.com \
--to=jdmason@us.ibm.com \
--cc=cramerj@intel.com \
--cc=ganesh.venkatesan@gmail.com \
--cc=greearb@candelatech.com \
--cc=netdev@oss.sgi.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;
as well as URLs for NNTP newsgroup(s).