From: Philip <phibo@phibo.org>
To: linux-kernel@vger.kernel.org
Subject: System.map
Date: Sun, 14 Oct 2007 19:07:38 +0200 [thread overview]
Message-ID: <20071014190738.58349165.phibo@phibo.org> (raw)
Hello
I want to write a script, which shows the name of the relevant kernel module for each listed pci device shown by 'lspci -m'. It's easy to find out the name of the corresponding module, if the driver has been compiled as a loadable kernel module: The file /lib/modules/$(uname -r)/modules.pcimap lists module names based on pci device's vendor -and device id (shown by 'lspci -n'). But how can I find out the name of the corresponding kernel module if the module has been compiled directly into the kernel ? I thought that I can find them in the kernel's machting System.map based on vendor -and device id as well. But I can't find those id's there. Where do I have to look for it ? I want to be informed by my script, if the driver (module) for a specific pci device is available as a loadable module, in-kernel module or not available at all.
Many thanks in advance for your answers and I hope, my question is not too annoying for you developer guys :-)
Cheers,
Phibo
next reply other threads:[~2007-10-14 17:43 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-14 17:07 Philip [this message]
2007-10-14 18:45 ` System.map Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2005-07-12 16:34 system.map vacant2005
2005-07-13 10:21 ` system.map Jan Engelhardt
[not found] ` <200507131244.08336.vacant2005@o2.pl>
2005-07-13 10:45 ` system.map Jacek Jabłoński
2005-07-13 10:56 ` system.map Arjan van de Ven
2005-07-13 11:04 ` system.map Jan Engelhardt
2005-07-13 11:27 ` system.map Russell King
2005-07-13 11:33 ` system.map Arjan van de Ven
2004-12-06 17:34 System.map Anoop T
2004-12-07 11:43 ` System.map Jan Engelhardt
[not found] <fa.ephh22v.1ljqarg@ifi.uio.no>
[not found] ` <fa.hmqrtsv.13jqup8@ifi.uio.no>
2002-01-02 21:14 ` system.map John Weber
2002-01-02 21:42 ` system.map Keith Owens
2002-01-02 19:11 system.map adrian kok
2002-01-02 19:26 ` system.map Timothy Covell
2002-01-02 19:39 ` system.map Tony Hoyle
2002-01-02 20:03 ` system.map Timothy Covell
2002-01-02 20:19 ` system.map Kilobug
2002-01-02 20:35 ` system.map Timothy Covell
2002-01-02 21:14 ` system.map Eric S. Johnson
2002-01-03 9:43 ` system.map Miquel van Smoorenburg
2002-01-02 20:25 ` system.map Tony Hoyle
2002-01-02 20:45 ` system.map Timothy Covell
2002-01-02 21:10 ` system.map Alan Cox
2002-01-02 23:07 ` system.map Nicholas Harring
2002-01-03 2:14 ` system.map Daniel Phillips
2002-01-03 15:54 ` system.map Albert D. Cahalan
2002-01-02 19:51 ` system.map Horst von Brand
2002-01-02 20:54 ` system.map Keith Owens
2002-01-02 21:13 ` system.map Timothy Covell
2002-01-02 23:01 ` system.map skidley
2002-01-02 23:14 ` system.map Timothy Covell
2002-01-02 21:17 ` system.map Albert D. Cahalan
2002-01-02 21:31 ` system.map Keith Owens
2002-01-02 22:09 ` system.map Nicholas Knight
2002-03-09 0:21 ` system.map H. Peter Anvin
2002-01-02 22:23 ` system.map Albert D. Cahalan
2002-01-02 23:38 ` system.map Marcel J.E. Mol
2002-01-02 19:30 ` system.map Sebastian Roth
2002-01-02 21:25 ` system.map Lionel Bouton
2002-01-02 22:15 ` system.map David Golden
2002-01-02 22:21 ` system.map Nick LeRoy
2002-01-02 22:29 ` system.map Lionel Bouton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071014190738.58349165.phibo@phibo.org \
--to=phibo@phibo.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.