From: Stephen Hemminger <shemminger@vyatta.com>
To: Mark Ryden <markryde@gmail.com>
Cc: Jeff Garzik <jeff@garzik.org>, netdev@vger.kernel.org
Subject: Re: [PATCH] ethtool: add names of newer Marvell chips
Date: Mon, 5 Apr 2010 10:34:03 -0700 [thread overview]
Message-ID: <20100405103403.2cde2af9@nehalam> (raw)
In-Reply-To: <q2sdac45061004030020n28a1ad17p71ed2c074ebb6450@mail.gmail.com>
On Sat, 3 Apr 2010 10:20:40 +0300
Mark Ryden <markryde@gmail.com> wrote:
> Hi,
>
> > + case 0xba: printf("Yukon Ultra 2"); break;
> > + case 0xbc: printf("Yukon Optima"); break;
>
> What about 0xbb?
> Is there ant reason for not using 0xbb for Yukon Optima?
>
> Is it something with blackberry (bb)? :-)
The value comes from a chip register.
The vendor hardware engineers didn't choose to use that version
yet.
next prev parent reply other threads:[~2010-04-05 17:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-02 15:16 [PATCH] ethtool: add names of newer Marvell chips Stephen Hemminger
2010-04-03 7:20 ` Mark Ryden
2010-04-05 17:34 ` Stephen Hemminger [this message]
2010-04-06 14:44 ` Jeff Garzik
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=20100405103403.2cde2af9@nehalam \
--to=shemminger@vyatta.com \
--cc=jeff@garzik.org \
--cc=markryde@gmail.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).