Which driver took effect?

From: Jan-Benedict Glaw (jbglaw@lug-owl.de)
Date: Wed Jan 10 2001 - 11:21:07 EST

Hi!

I'm building an installer (to install Linux as a .tar.gz off an
SMB share) usind a single floppy with some compiled-in network
drivers. These drivers are modular in the .tgz which gets uncompressed,
but most of them need parameters (normally, you have to supply
a base I/O address). Getting the address is no problem - ifconfig
tells you. But I can't see an easy way (neither in 2.2.x nor in
2.4.x) th be told "eth0 is driven by eepro, eth1 is driven by
ne, ...")

Parsing `dmesg` isn't fun at all (even not with restricted floppy
disk space to store a number of output variants), and different
drivers do have *very* different outputs (if they annouce themselves
at all).

So I'd like to know:

        - Can you tell me a smart way to see which driver handles
          which network interface?
        - Would a patch to add eg. /proc/net/drivers reporting:

                eth0, eepro, 0x300, 10
                eth1, ne, 0x240, 5

          be accepted? I think sth like that would be useful at all...

In 2.4.x, register_netdev() would be a good starting point to do
it...

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)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org Please read the FAQ at http://www.tux.org/lkml/

This archive was generated by hypermail 2b29 : Mon Jan 15 2001 - 21:00:27 EST