From: Val Henson <val@nmt.edu>
To: Tom Rini <trini@kernel.crashing.org>
Cc: jgarzik@mandrakesoft.com, becker@scyld.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Endian-ness bugs in yellowfin.c
Date: Fri, 14 Sep 2001 00:15:40 -0600 [thread overview]
Message-ID: <20010914001540.B2951@boardwalk> (raw)
In-Reply-To: <20010913195141.B799@boardwalk> <20010913193937.O21906@cpe-24-221-152-185.az.sprintbbd.net> <20010913205459.A1169@boardwalk> <20010913200237.P21906@cpe-24-221-152-185.az.sprintbbd.net>
In-Reply-To: <20010913200237.P21906@cpe-24-221-152-185.az.sprintbbd.net>; from trini@kernel.crashing.org on Thu, Sep 13, 2001 at 08:02:37PM -0700
On Thu, Sep 13, 2001 at 08:02:37PM -0700, Tom Rini wrote:
> On Thu, Sep 13, 2001 at 08:55:01PM -0600, Val Henson wrote:
> >
> > This is one of the "design decisions" I referred to. It makes no
> > sense to list a 100 Mbit driver under "Ethernet (1000 Mbit)". This is
> > my solution. This is the first case of a dual 1000/100 Mbit driver
> > and if there's a better way to handle it I'd like to hear it.
>
> Er, sungem does 10/100/1000 too I think.. (It's what's in the new G4
> towers..). IMHO, listing it once under the greatest makes sense. But
> sungem/gmac are under 10/100 I think.
You misunderstood what I meant. This is the first case of one driver
supporting two different cards, one 10/100 and one 10/100/1000. All
the gigabit cards are 10/100/1000 as far as I know. I still think the
driver should be listed in both the 100 Mbit and 1000 Mbit Ethernet
menu sections, unless someone comes up with a better idea.
-VAL
next prev parent reply other threads:[~2001-09-14 6:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-14 1:51 [PATCH] Endian-ness bugs in yellowfin.c Val Henson
2001-09-14 2:39 ` Tom Rini
2001-09-14 2:55 ` Val Henson
2001-09-14 3:02 ` Tom Rini
2001-09-14 5:01 ` Matthew Dharm
2001-09-14 6:12 ` Val Henson
2001-09-14 9:12 ` Alan Cox
2001-09-14 6:15 ` Val Henson [this message]
2001-09-14 6:47 ` Jeff Garzik
2001-09-14 8:07 ` Kai Henningsen
2001-09-14 20:20 ` Val Henson
2001-09-14 6:49 ` Jeff Garzik
2001-09-14 18:50 ` Cort Dougan
2001-09-14 20:20 ` Val Henson
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=20010914001540.B2951@boardwalk \
--to=val@nmt.edu \
--cc=becker@scyld.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.