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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux