Testing to see if a driver is loaded

Testing to see if a driver is loaded

[Robert Emanuele]

Greetings once again,

I was wondering if there is a simple way to test if a driver is loaded
from within another driver's probe?  I have one driver that depends on
another.  I see several *_find_device functions in
include/linux/device.h.  I haven't found a "find driver" nor an
arbitrary way of doing that.

Thanks for any guidance,

Rob

Re: Testing to see if a driver is loaded

[Robert Emanuele]

Hi Raj,

I appreciate the thought, but if you read my email closely you'll see
that I was looking for how to find if a driver is loaded into the
kernel (module or not) from within another driver's probe function.

--Rob

On Sun, Jun 13, 2010 at 11:48 PM, Raj singh <linux.rajsingh@gmail.com> wrote:
> Hi ,
>         You can use lsmod command...
>
> login as root & type lsmod | head -10...it will show you a list of drivers
> currently loaded in your kernel....
>
>
> Raj.
>
> On Sun, Jun 13, 2010 at 10:03 AM, Robert Emanuele <rob@emanuele.us> wrote:
>>
>> Greetings once again,
>>
>> I was wondering if there is a simple way to test if a driver is loaded
>> from within another driver's probe?  I have one driver that depends on
>> another.  I see several *_find_device functions in
>> include/linux/device.h.  I haven't found a "find driver" nor an
>> arbitrary way of doing that.
>>
>> Thanks for any guidance,
>>
>> Rob
>> --
>> 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/
>
>

Re: Testing to see if a driver is loaded

[Robert Hancock]

On 06/12/2010 10:33 PM, Robert Emanuele wrote:
> Greetings once again,
>
> I was wondering if there is a simple way to test if a driver is loaded
> from within another driver's probe?  I have one driver that depends on
> another.  I see several *_find_device functions in
> include/linux/device.h.  I haven't found a "find driver" nor an
> arbitrary way of doing that.
>
> Thanks for any guidance,

There's not a simple answer, it depends what you are trying to achieve 
(i.e. in what way is the driver dependent on the other one..)