All of lore.kernel.org
 help / color / mirror / Atom feed
From: Val Henson <val@nmt.edu>
To: Tom Rini <trini@kernel.crashing.org>,
	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:12:03 -0600	[thread overview]
Message-ID: <20010914001201.A2951@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> <20010913220118.A647@one-eyed-alien.net>
In-Reply-To: <20010913220118.A647@one-eyed-alien.net>; from mdharm-kernel@one-eyed-alien.net on Thu, Sep 13, 2001 at 10:01:18PM -0700

On Thu, Sep 13, 2001 at 10:01:18PM -0700, Matthew Dharm wrote:
> I would agree that listing them under the highest capable is probably the
> best.  It is, at least, consistent with the 10/100 cards.

I'm interested to hear why you think this is better than listing the
card under both of the 100 and 1000 Mbit categories (as the patch I
sent does it).  Also, we are not talking about one 10/100/1000 card,
we are talking about one driver that supports two separate cards, one
10/100/1000 and one 10/100.

-VAL

> Also, people will pick up the card, think "gigabit ethernet", and then look
> under the 1000 section.  I don't think anyone will really think GigE and
> then look under 10/100.
> 
> The Intel 82543 and 82544 gigabit parts are all 10/100/1000 -- I'll be
> writing a driver for those in a few weeks if nobody beats me to it, so I
> think it would be good to settle this.
> 
> Matt
> 
> 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:
> > > On Thu, Sep 13, 2001 at 07:39:37PM -0700, Tom Rini wrote:
> > > > On Thu, Sep 13, 2001 at 07:51:41PM -0600, Val Henson wrote:
> > > > > -      tristate '  Symbios 53c885 (Synergy ethernet) support' CONFIG_NCR885E
> > > > > +      tristate '  Symbios 53c885 (Synergy ethernet) support' CONFIG_YELLOWFIN
> > > > 
> > > > Since you're killing this, why not just remove this question entirely?
> > > 
> > > 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.
> > 
> > -- 
> > Tom Rini (TR1265)
> > http://gate.crashing.org/~trini/
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> 
> -- 
> Matthew Dharm                              Home: mdharm-usb@one-eyed-alien.net 
> Maintainer, Linux USB Mass Storage Driver
> 
> C:  They kicked your ass, didn't they?
> S:  They were cheating!
> 					-- The Chief and Stef
> User Friendly, 11/19/1997



  reply	other threads:[~2001-09-14  6:25 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 [this message]
2001-09-14  9:12         ` Alan Cox
2001-09-14  6:15       ` Val Henson
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=20010914001201.A2951@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.