Date: Thu, 11 Nov 2004 16:48:18 -0500 (EST)
From: linux-os <linux-os@chaos.analogic.com>
Reply-To: linux-os@analogic.com
To: Anthony Samsung <anthony.samsung@gmail.com>
cc: linux-kernel@vger.kernel.org
Subject: Re: network interface to driver and pci slot mapping
In-Reply-To: <8874763604111113281b1cf9a5@mail.gmail.com>
Message-ID: <Pine.LNX.4.61.0411111640470.11012@chaos.analogic.com>
References: <8874763604111113281b1cf9a5@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1243
Lines: 32

On Thu, 11 Nov 2004, Anthony Samsung wrote:

> Given an interface name (like eth0), how do I determine:
> The name of the driver (module) for this interface.
> The PCI address for this interface, if relevant.
>
> ?
>
> I need something that works non-destructively on a live system, that
> isn't broken by nameif, and has a strong chance of producing a correct
> result. In particular, parsing syslog is out. There's no consistency
> in the format of messages and there's no guarantee the logs from
> bootup will still be around. And the interface may have been renamed
> since then.

If the eth0 device is a module, it's in /etc/modprobe.conf, previous
versions used /etc/modules.conf.
Once you have its module name you can use other resources like

/sys/bus/pci/drivers/MODULENAME


Cheers,
Dick Johnson
Penguin : Linux version 2.6.9 on an i686 machine (5537.79 BogoMips).
  Notice : All mail here is now cached for review by John Ashcroft.
                  98.36% of all statistics are fiction.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/