netdev
[Top] [All Lists]

Re: dev->name in /proc/ioports (was: Re: [patch] NE2000)

To: Jeff Garzik <jgarzik@xxxxxxxxxxxxxxxx>
Subject: Re: dev->name in /proc/ioports (was: Re: [patch] NE2000)
From: Paul Gortmaker <p_gortmaker@xxxxxxxxx>
Date: Mon, 06 Nov 2000 13:03:45 -0500
Cc: Donald Becker <becker@xxxxxxxxx>, linux-net@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
References: <Pine.LNX.4.10.10011021935530.11540-100000@vaio.greennet> <3A020C19.4C4B3F66@mandrakesoft.com> <3A0663E1.35A49246@yahoo.com> <3A067F15.2E474B36@mandrakesoft.com>
Sender: owner-netdev@xxxxxxxxxxx
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


<Prev in Thread] Current Thread [Next in Thread>