Jeff Garzik wrote:
>
> Paul Gortmaker wrote:
> > But the only reliable way to query the kernel as to what compiled in ISA
^^^^^^^^
> > net driver is installed is by a model name in /proc/[ioports,interrupts]
> > (Yes, I know, a minor issue...)
>
> I always use 'dmesg' for this...
It isn't reliable - some installs did a "dmesg -c" at boot IIRC, or the
ring buf may have already wrapped with crud like VFS disk change
messages.
> > Also, the trend for /proc/ioports (and interrupts) in other parts of the
> > kernel still appears to be based on hardware/model names and not kernel
> > device names, e.g. serial and not ttyS*, BusLogic BT-XXX and not scsi0,
> > soundblaster and not /dev/audio, etc. -- hence 3c509 and not eth0 would
> > be consistent?
>
> Especially for interrupts, it would be much smarter for the other
> devices to indicate their device, since that allows you to differentiate
> between adapters of the same type.
Ok - I still think consistency is a worthwhile goal. So I guess we
(in 2.5.x) will have to extend the scope of settling on the device name
outside of drivers/net (assuming nobody else has sufficient reasons to
stick with model names instead).
Paul.
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
