On Wed, Oct 24, 2012 at 1:42 PM, Greg Kroah-Hartman
wrote:
> Yes, but why? Let's not overdesign this, get the basics working and
> then, if someone really needs it, we can add it.
OK, I will remove the kernel parameter and related documentation,
and just keep it as module parameter, sorry about
On Wed, Oct 24, 2012 at 11:31:16AM +0800, Ming Lei wrote:
> On Wed, Oct 24, 2012 at 11:18 AM, Greg Kroah-Hartman
> wrote:
> >
> > Ick, no, not another kernel boot parameter. I would prefer the /proc/
> > file solution instead, just like /proc/sys/kernel/hotplug is.
>
> OK, got it, but we could u
On Wed, Oct 24, 2012 at 11:18 AM, Greg Kroah-Hartman
wrote:
>
> Ick, no, not another kernel boot parameter. I would prefer the /proc/
> file solution instead, just like /proc/sys/kernel/hotplug is.
OK, got it, but we could use the module parameter(firmware_class.path
via kernel command) to custo
On Wed, Oct 24, 2012 at 10:49:53AM +0800, Ming Lei wrote:
> This patch introduces one kernel parameter of 'fw_path' to support
> customizing firmware image search path, so that people can use its
> own firmware path if the default built-in paths can't meet their demand[1].
>
> [1], https://lkml.or
This patch introduces one kernel parameter of 'fw_path' to support
customizing firmware image search path, so that people can use its
own firmware path if the default built-in paths can't meet their demand[1].
[1], https://lkml.org/lkml/2012/10/11/337
Cc: Linus Torvalds
Signed-off-by: Ming Lei
5 matches
Mail list logo
