* CONFIG_FW_LOADER
@ 2009-04-04 18:05 Adrian McMenamin
2009-04-05 4:18 ` CONFIG_FW_LOADER Marcel Holtmann
0 siblings, 1 reply; 3+ messages in thread
From: Adrian McMenamin @ 2009-04-04 18:05 UTC (permalink / raw)
To: LKML
Currently the help for this states:
CONFIG_FW_LOADER:
This option is provided for the case where no in-kernel-tree modules
require userspace firmware loading support, but a module built outside
the kernel tree does.
Is it just me or is this somewhat misleading? Don't all modules that
load firmware from userspace require this?
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: CONFIG_FW_LOADER
2009-04-04 18:05 CONFIG_FW_LOADER Adrian McMenamin
@ 2009-04-05 4:18 ` Marcel Holtmann
2009-04-05 11:01 ` CONFIG_FW_LOADER Adrian McMenamin
0 siblings, 1 reply; 3+ messages in thread
From: Marcel Holtmann @ 2009-04-05 4:18 UTC (permalink / raw)
To: Adrian McMenamin; +Cc: LKML
Hi Adrian,
> Currently the help for this states:
>
>
> CONFIG_FW_LOADER:
> This option is provided for the case where no in-kernel-tree modules
> require userspace firmware loading support, but a module built outside
> the kernel tree does.
>
>
> Is it just me or is this somewhat misleading? Don't all modules that
> load firmware from userspace require this?
all drivers that do use 'select FW_LOADER' and so they trigger building
this module anyway. The config option is purely if you have a driver
that is built outside the tree and wanna use request_firmware().
Regards
Marcel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: CONFIG_FW_LOADER
2009-04-05 4:18 ` CONFIG_FW_LOADER Marcel Holtmann
@ 2009-04-05 11:01 ` Adrian McMenamin
0 siblings, 0 replies; 3+ messages in thread
From: Adrian McMenamin @ 2009-04-05 11:01 UTC (permalink / raw)
To: Marcel Holtmann; +Cc: LKML
On Sun, 2009-04-05 at 06:18 +0200, Marcel Holtmann wrote:
> Hi Adrian,
>
> > Currently the help for this states:
> >
> >
> > CONFIG_FW_LOADER:
> > This option is provided for the case where no in-kernel-tree modules
> > require userspace firmware loading support, but a module built outside
> > the kernel tree does.
> >
> >
> > Is it just me or is this somewhat misleading? Don't all modules that
> > load firmware from userspace require this?
>
> all drivers that do use 'select FW_LOADER' and so they trigger building
> this module anyway. The config option is purely if you have a driver
> that is built outside the tree and wanna use request_firmware().
>
OK. Guess the issue is that my module doesn't select this. I'll patch
that.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2009-04-05 11:01 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-04-04 18:05 CONFIG_FW_LOADER Adrian McMenamin
2009-04-05 4:18 ` CONFIG_FW_LOADER Marcel Holtmann
2009-04-05 11:01 ` CONFIG_FW_LOADER Adrian McMenamin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox