RE: [PATCH] firmware loader: allow disabling of udev as firmware loader

From: B_B_Singh
Date: Mon Jun 09 2014 - 10:12:15 EST


Hi Tom,

Older userspace or existing DUP's doesn't work with your patch & CONFIG_FW_LOADER_USER_HELPER=n.

I will give a try with https://lkml.org/lkml/2014/6/4/327 new patch & let you know ASAP.

Regards
Balaji Singh


-----Original Message-----
From: Tom Gundersen [mailto:teg@xxxxxxx]
Sent: Monday, June 09, 2014 7:23 PM
To: Singh, B B
Cc: LKML; Ming Lei; Greg KH; Abhay Salunke; Stefan Roese; Arnd Bergmann; Kay Sievers; Domsch, Matt; Gowda, Srinivas G; Hayes, Stuart
Subject: Re: [PATCH] firmware loader: allow disabling of udev as firmware loader

Hi Balaji,

On Mon, Jun 9, 2014 at 3:26 PM, wrote:
> The existing BIOS-DUP's will not work on latest kernel, which has
> CONFIG_FW_LOADER_USER_HELPER=n configured in Kernel config by default
> which is not expected by the dell_rbu.
>
>
>
> We have made a changes in BIOS-Dell Update Package so that BIOS-DUP
> will pick the payload from the /lib/firmware/ path & update the BIOS
> even when CONFIG_FW_LOADER_USER_HELPER=n is configured .
>
>
>
> We have tested this patch
> http://www.spinics.net/lists/kernel/msg1755247.html with latest BIOS
> Dell Update Package (which has new implementation for the BIOS update
> i.e, copying the BIOS payload in /lib/firmware path & dell_rbu picks the payload
> from the same path) & with stable upstream kernel-3.14.5 & we don't
> see any negative effects/errors for dell_rbu.

Thanks for testing! May I ask if the dell_rbu still works with my patch and CONFIG_FW_LOADER_USER_HELPER=n with the old userspace? The intention was that you should not need to change anything in userspace at all.

By the way, there is now a new version of this patch:
, which should allow your (old or new userspace) Dell RBU to work with FW_LOADER_USER_HELPER_FALLBACK=n, so maybe it would be best to test that instead.

Cheers,

Tom
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/