Every half-decent installer autodetects all PCI devices. AND had lspci
installed in the install image.
> Next problem is that some drivers want to print "user readable" hardware
> name to user, and although some have its own name database (e100), some
> use name from pcidev...
Ugh :-/ That's a reason to keep it around then.
>> > I do grant you it would make various __init sections and in-memory
>> > structures smaller if we eliminated the names... do we want to? Sure we
>> > have lseisa and lspci and lsusb, et. al. Does that obviate the need for a
>> > simple summary of attached hardware?
>>
>> IMO, yes, since those tools provide the summary, and exist almost purely in
>> userspace. I forgot to mention in the orginal email that we could also drop
>> the PCI names database, right? This would save a considerable amount in the
>> kernel image alone..
>
> If you want, make it user configurable like it was during 2.2.x. But
> I personally prefer descriptive names and system overview I can parse
> without having mounted /usr to get working lspci.
lspci should be installed in /sbin.
-- Erik Hensema (erik@hensema.net) - 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/