Netdev List
 help / color / mirror / Atom feed
From: Krzysztof Halasa <khc@pm.waw.pl>
To: Stefan Schmidt <stefan@datenfreihafen.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	aabdulla@nvidia.com, netdev@vger.kernel.org
Subject: Re: forcedeth: Reside in 100Mbit Kconfig but also supports 1000Mbit cards
Date: Mon, 28 May 2007 22:02:56 +0200	[thread overview]
Message-ID: <m3ejl0u367.fsf@maximus.localdomain> (raw)
In-Reply-To: <20070527005609.GB9566@datenfreihafen.org> (Stefan Schmidt's message of "Sun, 27 May 2007 02:56:09 +0200")

Stefan Schmidt <stefan@datenfreihafen.org> writes:

> I still like the partition by speed.

Me 2

> It makes it a lot easier to find
> the right driver in the bunch of available ones.

Sure. Unless you have a 100 Mb/s card and you don't know the same
driver works with newer 1000 Mb/s models.

IOW - questionable.

> A solution like a
> Kconfig entry symlink for driver which needs to support cards in two
> or more categories would be my favorite.

It would be a total mess.


However, some clever conditionals could make it better.
One menu for both 100 and 1000 Mb/s, and something like:

tristate 100Mbps (Y/N/M)
tristate 1000Mbps (Y/N/M)

...
if 100Mbps
	Realtek 8139
	Intel E100
fi

if 100Mbps || 1000Mbps
	forcedeath
	some_SIS_driver
	etc.
fi

if 1000Mbps
	E1000
	...

Probably 10 Mbps drivers could lead the list. You could check for PCI,
ISA and what not.
This way each driver has only one entry, but if you know you have,
say, 1 Gb/s Ethernet card only you can select 1 Gb/s and don't
worry about 100-Mbps NVidias.

I'd include that Tulip thing, too - no need for a separate menu
(the directory is a different thing).
-- 
Krzysztof Halasa

      reply	other threads:[~2007-05-29  3:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-26 23:07 forcedeth: Reside in 100Mbit Kconfig but also supports 1000Mbit cards Stefan Schmidt
2007-05-27  0:29 ` Randy Dunlap
2007-05-27  0:56   ` Stefan Schmidt
2007-05-28 20:02     ` Krzysztof Halasa [this message]

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=m3ejl0u367.fsf@maximus.localdomain \
    --to=khc@pm.waw.pl \
    --cc=aabdulla@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=stefan@datenfreihafen.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