From: Tom Gundersen <teg@jklm.no>
To: B_B_Singh@dell.com
Cc: LKML <linux-kernel@vger.kernel.org>,
Ming Lei <ming.lei@canonical.com>,
Greg KH <gregkh@linuxfoundation.org>,
Abhay Salunke <Abhay_Salunke@dell.com>, Stefan Roese <sr@denx.de>,
Arnd Bergmann <arnd@arndb.de>, Kay Sievers <kay@vrfy.org>,
Matt_Domsch@dell.com, Srinivas_G_Gowda@dell.com,
Stuart_Hayes@dell.com
Subject: Re: [PATCH] firmware loader: allow disabling of udev as firmware loader
Date: Mon, 9 Jun 2014 15:53:11 +0200 [thread overview]
Message-ID: <CAG-2HqUDQ3e-cq4y3zgehz6J8E6LsTCUfqvMEqPEqG7aBmEeRg@mail.gmail.com> (raw)
In-Reply-To: <8B2F6FFD0BD1E448853114367400A37306FCD2E023@BLRX7MCDC203.AMER.DELL.COM>
Hi Balaji,
On Mon, Jun 9, 2014 at 3:26 PM, <B_B_Singh@dell.com> 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:
<https://lkml.org/lkml/2014/6/4/327>, 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
next parent reply other threads:[~2014-06-09 13:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8B2F6FFD0BD1E448853114367400A37306FCD2E023@BLRX7MCDC203.AMER.DELL.COM>
2014-06-09 13:53 ` Tom Gundersen [this message]
2014-06-09 14:01 ` [PATCH] firmware loader: allow disabling of udev as firmware loader B_B_Singh
2014-06-09 15:50 ` Tom Gundersen
2014-06-10 15:13 ` B_B_Singh
2014-06-16 14:27 ` Tom Gundersen
2014-06-16 14:08 ` B_B_Singh
2014-06-16 14:28 ` Tom Gundersen
2014-06-09 13:44 B_B_Singh
-- strict thread matches above, loose matches on Subject: below --
2014-06-02 18:24 Tom Gundersen
2014-06-04 14:20 ` Takashi Iwai
2014-06-04 14:31 ` Takashi Iwai
2014-06-04 14:35 ` Tom Gundersen
2014-06-04 14:34 ` Tom Gundersen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAG-2HqUDQ3e-cq4y3zgehz6J8E6LsTCUfqvMEqPEqG7aBmEeRg@mail.gmail.com \
--to=teg@jklm.no \
--cc=Abhay_Salunke@dell.com \
--cc=B_B_Singh@dell.com \
--cc=Matt_Domsch@dell.com \
--cc=Srinivas_G_Gowda@dell.com \
--cc=Stuart_Hayes@dell.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=kay@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@canonical.com \
--cc=sr@denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.