From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.7-rc2
Date: Tue, 08 Jun 2004 13:02:42 -0400 [thread overview]
Message-ID: <ca4r6t$p16$1@gatekeeper.tmr.com> (raw)
In-Reply-To: <200406041706.27716.vda@port.imtp.ilyichevsk.odessa.ua>
Denis Vlasenko wrote:
> On Wednesday 02 June 2004 17:37, Thomas Zehetbauer wrote:
>
>>http://bugzilla.kernel.org/show_bug.cgi?id=2819
>>
>>Make oldconfig silently disabled support for my CONFIG_TIGON3 NIC.
>>
>>It seems that it depends on CONFIG_NET_GIGE which in turn depends on
>>CONFIG_NET_ETHERNET which was not required in 2.6.6 kernel.
>>
>>Tom
>
>
> Many days ago I read on lkml that separating 10,100 and 1000 Mbit
> ethernet is not really justified. There are devices which have
> 100 and 1000 variants.
>
> Just keeping all ethernet devices in one menu sounds sane to me.
There are other issues with the build process, when a driver supports a
chipset used in several products there's no reasonable way to find out
which driver should be used, and as you say the split of speed makes
less and less sense, and will just get worse when 10Ge is more common.
The solution may be an external table, program, or whatever, since the
situation changes as drivers are modified to support new models,
chipsets move to new vendors, etc. But it would be *really nice* to find
the 3c940 with 3COM drivers, instead of grepping driver source and
looking at spec sheets to find out that the driver is called something
like sk98lin, it's in an unobvious place and has a name unrelated to 3COM.
Here's a suggestion if someone wants to do something about this, like
LDP. Produce a CSV list of vendor name, like 3c940, name used for config
in the menu, module name and symbol in the .config file. Would let users
find things a lot faster, and could be used with grep as well as some
spreadsheet tool.
--
-bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
last possible moment - but no longer" -me
next prev parent reply other threads:[~2004-06-08 17:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-30 6:52 Linux 2.6.7-rc2 Linus Torvalds
2004-05-30 7:56 ` Danny ter Haar
2004-05-30 11:09 ` Francois Romieu
2004-05-30 13:16 ` Danny ter Haar
2004-05-30 13:24 ` Danny ter Haar
2004-05-30 16:26 ` Malte Schröder
2004-05-30 17:26 ` Jeff Garzik
2004-05-31 9:21 ` Peter Osterlund
2004-05-31 9:27 ` Andrew Morton
2004-05-31 16:58 ` Linus Torvalds
2004-05-31 22:04 ` Peter Osterlund
2004-06-03 20:01 ` Flavio Stanchina
2004-06-01 3:44 ` Linux 2.6.7-rc2 (compile stats) John Cherry
2004-06-01 16:07 ` 2.6.7-rc2: .bss.page_aligned warning with gcc 2.95 Adrian Bunk
2004-06-02 14:37 ` Linux 2.6.7-rc2 Thomas Zehetbauer
2004-06-04 14:06 ` Denis Vlasenko
2004-06-08 17:02 ` Bill Davidsen [this message]
2004-06-08 18:02 ` David Ford
2004-06-09 6:37 ` sk98lin (was: Re: Linux 2.6.7-rc2) Geert Uytterhoeven
2004-06-10 15:03 ` SCSI_DPT_I2O " Geert Uytterhoeven
2004-06-10 15:33 ` ide-proc.c " Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2004-05-31 12:20 Linux 2.6.7-rc2 Albert Cahalan
2004-05-31 16:53 ` Linus Torvalds
2004-05-31 15:12 ` Albert Cahalan
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='ca4r6t$p16$1@gatekeeper.tmr.com' \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.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