From: James Bottomley <James.Bottomley-d9PhHud1JfjCXq6kfMZ53/egYHeGw8Jk@public.gmane.org>
To: Parmeshwr_Prasad-DYMqY+WieiM@public.gmane.org
Cc: linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Matt Fleming
<matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
Subject: Re: Capsule patches
Date: Wed, 27 May 2015 10:58:30 -0700 [thread overview]
Message-ID: <1432749510.2194.35.camel@HansenPartnership.com> (raw)
In-Reply-To: <EAEC0BCD44614F499E7CCE37C3B71F113806869D60-6n1rj5y50trWnfa2oNyE5AVY21JRvFwKV6yJEvX+wlw@public.gmane.org>
[adding linux-efi because that's where the experts hang out]
On Mon, 2015-05-25 at 16:14 +0530, Parmeshwr_Prasad-DYMqY+WieiM@public.gmane.org wrote:
> Hi James,
>
> I am from dell.
> I was working on Capsule feature. I got some patches from you which
> supports user space interface for capsule.
> I have applied those patches on 4.0 kernel and booted my server. I am
> getting /sys/.../update entry to give capsule as interface.
>
> I am attaching your patches.
> Along with this I have applied patched shared by Mutt.
>
> I have done cat fw_file > /sys/firmware/capsule/update to give capsule
> file.
>
> After doing this my kernel is hang. Any help how to debug this ?
The patch was just a RFC demonstrating how the user interface would
work ... and to secure agreement around that, since it had been one of
the contentious issues.
However, I'm fairly certain the back end (the call into ACPI) also
doesn't work properly. Matt Fleming has some ideas about fixing that
up. You'll need both pieces to get this fully functional.
James
parent reply other threads:[~2015-05-27 17:58 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <EAEC0BCD44614F499E7CCE37C3B71F113806869D60-6n1rj5y50trWnfa2oNyE5AVY21JRvFwKV6yJEvX+wlw@public.gmane.org>]
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=1432749510.2194.35.camel@HansenPartnership.com \
--to=james.bottomley-d9phhud1jfjcxq6kfmz53/egyhegw8jk@public.gmane.org \
--cc=Parmeshwr_Prasad-DYMqY+WieiM@public.gmane.org \
--cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).