Re: Which driver took effect?

[Jan-Benedict Glaw <jbglaw@lug-owl.de>]

[-- Attachment #1: Type: text/plain, Size: 1300 bytes --]

On Thu, Jan 11, 2001 at 12:33:22AM +0330, tnvander@chello.nl wrote:
> Hello,
> 
> I looked at some outputs and 
> /proc/interrupts
> /proc/ioports
> /proc/iomem

It's all messy and inconsistent;(

> And scanning dmesg is indeed just the road to ugly hacks, although
> it does seem common practice to report as <interface:drivername at ...>
> so that perhaps an interface name can be linked to a drivername and

Well, some do it that way;)

> both can be used to scan thru /proc/ioports and /proc/interrupts...
> Yes, sounds terribly hacky, sounds like perl or python are wanted
> for this, sounds like a job too large for a bootdisk...

Getting the base IO address is no problem:

/sbin/ifconfig eth0 | grep "Base address" | cut -f 3 -d ':'

...but getting the appropriate driver is not that easy;(

> I'm sorry that I can't help you! I thought that /proc/interrupts
> etc was good advice and then found out that it's as messy :-(

That's just what I thought;)

MfG, JBG

-- 
Fehler eingestehen, Größe zeigen: Nehmt die Rechtschreibreform zurück!!!
/* Jan-Benedict Glaw <jbglaw@lug-owl.de> -- +49-177-5601720 */
keyID=0x8399E1BB fingerprint=250D 3BCF 7127 0D8C A444 A961 1DBD 5E75 8399 E1BB
     "insmod vi.o and there we go..." (Alexander Viro on linux-kernel)

[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]