Subject: Re: CONFIG_FW_LOADER
From: Adrian McMenamin <adrian@newgolddream.dyndns.info>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: LKML <linux-kernel@vger.kernel.org>
In-Reply-To: <1238905089.19390.7.camel@violet>
References: <1238868348.6489.8.camel@localhost.localdomain>
	 <1238905089.19390.7.camel@violet>
Content-Type: text/plain
Date: Sun, 05 Apr 2009 12:01:15 +0100
Message-Id: <1238929275.6511.2.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 992
Lines: 28

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.

--
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/