linux-kernel - Re: CONFIG_FW

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1238929275.6511.2.camel@localhost.localdomain>
Date:	Sun, 05 Apr 2009 12:01:15 +0100
From:	Adrian McMenamin <adrian@...golddream.dyndns.info>
To:	Marcel Holtmann <marcel@...tmann.org>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: CONFIG_FW_LOADER

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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/