From: "Arend van Spriel" <arend@broadcom.com>
To: "Thiago Farina" <tfransosi@gmail.com>
Cc: "linux list" <linux-kernel@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Subject: Re: listing drivers
Date: Wed, 23 Jan 2013 18:24:06 +0100 [thread overview]
Message-ID: <51001CB6.2090900@broadcom.com> (raw)
In-Reply-To: <CACnwZYeS2=LJuuHJhpTtdijj+xXYiYZ2_hZNShGo9q8_J-pkMQ@mail.gmail.com>
On 01/23/2013 04:30 PM, Thiago Farina wrote:
> Hi,
>
> On Tue, Jan 22, 2013 at 12:27 PM, Arend van Spriel <arend@broadcom.com> wrote:
>> On 01/22/2013 02:46 PM, Thiago Farina wrote:
>>> Hi folks,
>>>
>>> Is there a way to list the drivers installed/used in my desktop and
>>> map them (the path) to their source code in the linux kernel tree?
>>
>> This might work for you (if using bash):
>>
>> for m in $(cat /proc/modules | gawk '{ print $1; }');do modinfo $m |
>> grep 'filename:'; done
>>
> Thanks a lot Arend! That is exactly what I wanted ;)
You are welcome. Of course, not all modules are (device) drivers.
Gr. AvS
> --
> Thiago
>
prev parent reply other threads:[~2013-01-23 17:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 13:46 listing drivers Thiago Farina
2013-01-22 14:27 ` Arend van Spriel
2013-01-23 6:16 ` zhuyj
2013-01-23 15:30 ` Thiago Farina
2013-01-23 17:24 ` Arend van Spriel [this message]
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=51001CB6.2090900@broadcom.com \
--to=arend@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tfransosi@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox