* [PATCH] ethtool: add names of newer Marvell chips
@ 2010-04-02 15:16 Stephen Hemminger
2010-04-03 7:20 ` Mark Ryden
2010-04-06 14:44 ` Jeff Garzik
0 siblings, 2 replies; 4+ messages in thread
From: Stephen Hemminger @ 2010-04-02 15:16 UTC (permalink / raw)
To: Jeff Garzik; +Cc: netdev
Fill in names of newer chips.
Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
diff --git a/marvell.c b/marvell.c
index 6696e0a..af38c21 100644
--- a/marvell.c
+++ b/marvell.c
@@ -184,6 +184,9 @@ static void dump_mac(const u8 *r)
case 0xb6: printf("Yukon-2 EC"); break;
case 0xb7: printf("Yukon-2 FE"); break;
case 0xb8: printf("Yukon-2 FE Plus"); break;
+ case 0xb9: printf("Yukon Supreme"); break;
+ case 0xba: printf("Yukon Ultra 2"); break;
+ case 0xbc: printf("Yukon Optima"); break;
default: printf("(Unknown)"); break;
}
--
1.6.3.3
^ permalink raw reply related [flat|nested] 4+ messages in thread* Re: [PATCH] ethtool: add names of newer Marvell chips
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
2010-04-06 14:44 ` Jeff Garzik
1 sibling, 1 reply; 4+ messages in thread
From: Mark Ryden @ 2010-04-03 7:20 UTC (permalink / raw)
To: Stephen Hemminger; +Cc: Jeff Garzik, netdev
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)? :-)
Mark
On Fri, Apr 2, 2010 at 6:16 PM, Stephen Hemminger <shemminger@vyatta.com> wrote:
> Fill in names of newer chips.
>
> Signed-off-by: Stephen Hemminger <shemminger@vyatta.com>
>
>
> diff --git a/marvell.c b/marvell.c
> index 6696e0a..af38c21 100644
> --- a/marvell.c
> +++ b/marvell.c
> @@ -184,6 +184,9 @@ static void dump_mac(const u8 *r)
> case 0xb6: printf("Yukon-2 EC"); break;
> case 0xb7: printf("Yukon-2 FE"); break;
> case 0xb8: printf("Yukon-2 FE Plus"); break;
> + case 0xb9: printf("Yukon Supreme"); break;
> + case 0xba: printf("Yukon Ultra 2"); break;
> + case 0xbc: printf("Yukon Optima"); break;
> default: printf("(Unknown)"); break;
> }
>
> --
> 1.6.3.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: [PATCH] ethtool: add names of newer Marvell chips
2010-04-03 7:20 ` Mark Ryden
@ 2010-04-05 17:34 ` Stephen Hemminger
0 siblings, 0 replies; 4+ messages in thread
From: Stephen Hemminger @ 2010-04-05 17:34 UTC (permalink / raw)
To: Mark Ryden; +Cc: Jeff Garzik, netdev
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.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH] ethtool: add names of newer Marvell chips
2010-04-02 15:16 [PATCH] ethtool: add names of newer Marvell chips Stephen Hemminger
2010-04-03 7:20 ` Mark Ryden
@ 2010-04-06 14:44 ` Jeff Garzik
1 sibling, 0 replies; 4+ messages in thread
From: Jeff Garzik @ 2010-04-06 14:44 UTC (permalink / raw)
To: Stephen Hemminger; +Cc: netdev
On 04/02/2010 11:16 AM, Stephen Hemminger wrote:
> Fill in names of newer chips.
>
> Signed-off-by: Stephen Hemminger<shemminger@vyatta.com>
applied
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2010-04-06 14:44 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2010-04-06 14:44 ` Jeff Garzik
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).