Re: forcedeth: Reside in 100Mbit Kconfig but also supports 1000Mbit cards

2007-05-28 Thread Krzysztof Halasa
Stefan Schmidt [EMAIL PROTECTED] 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
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


forcedeth: Reside in 100Mbit Kconfig but also supports 1000Mbit cards

2007-05-26 Thread Stefan Schmidt
Hello.

I just needed some to tƣme to find out that the forcedeth driver I
need for my dual-port 1000Mbit card on a asus M2N-SLI deluce mainboard
resides in the 100Mbit category.

Is there a special reason for example 10/100Mbit only cards that work
with forcedeth? If all cards are 1000Mbit I would just move the
Kconfig entry over.

What would be the best way to deal with this if there are some
10/100Mbit cards which use the same driver as 1000Mbit cards?

regards
Stefan Schmidt
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: forcedeth: Reside in 100Mbit Kconfig but also supports 1000Mbit cards

2007-05-26 Thread Randy Dunlap
On Sun, 27 May 2007 01:07:50 +0200 Stefan Schmidt wrote:

 Hello.
 
 I just needed some to tƣme to find out that the forcedeth driver I
 need for my dual-port 1000Mbit card on a asus M2N-SLI deluce mainboard
 resides in the 100Mbit category.
 
 Is there a special reason for example 10/100Mbit only cards that work
 with forcedeth? If all cards are 1000Mbit I would just move the
 Kconfig entry over.
 
 What would be the best way to deal with this if there are some
 10/100Mbit cards which use the same driver as 1000Mbit cards?

There has been some mention of dropping the 10/100 and 1000
categories and just merging all of them together.
Makes sense to me.


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: forcedeth: Reside in 100Mbit Kconfig but also supports 1000Mbit cards

2007-05-26 Thread Stefan Schmidt
Hello.

On Sat, 2007-05-26 at 17:29, Randy Dunlap wrote:
 On Sun, 27 May 2007 01:07:50 +0200 Stefan Schmidt wrote:
 
  
  What would be the best way to deal with this if there are some
  10/100Mbit cards which use the same driver as 1000Mbit cards?
 
 There has been some mention of dropping the 10/100 and 1000
 categories and just merging all of them together.
 Makes sense to me.

I still like the partition by speed. It makes it a lot easier to find
the right driver in the bunch of available ones. A solution like a
Kconfig entry symlink for driver which needs to support cards in two
or more categories would be my favorite.

regards
Stefan Schmidt
-
To unsubscribe from this list: send the line unsubscribe netdev in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html