netdev
[Top] [All Lists]

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

To: Paul Gortmaker <p_gortmaker@xxxxxxxxx>
Subject: Re: dev->name in /proc/ioports (was: Re: [patch] NE2000)
From: Jeff Garzik <jgarzik@xxxxxxxxxxxxxxxx>
Date: Mon, 06 Nov 2000 04:51:17 -0500
Cc: Donald Becker <becker@xxxxxxxxx>, linux-net@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
Organization: MandrakeSoft
References: <Pine.LNX.4.10.10011021935530.11540-100000@vaio.greennet> <3A020C19.4C4B3F66@mandrakesoft.com> <3A0663E1.35A49246@yahoo.com>
Sender: owner-netdev@xxxxxxxxxxx
Paul Gortmaker wrote:
> Something to consider (while still restricting this discussion to ISA
> junk), you can always get ethN <---> irq/ioport mapping via. SIOCGIFMAP.
> 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...


> 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.

        Jeff


-- 
Jeff Garzik             | Dinner is ready when
Building 1024           | the smoke alarm goes off.
MandrakeSoft            |       -/usr/games/fortune

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