From: Bryan O'Donoghue <pure.logic@nexus-software.ie>
To: "Kweh, Hock Leong" <hock.leong.kweh@intel.com>,
Borislav Petkov <bp@alien8.de>
Cc: Matt Fleming <matt@console-pimps.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Ong, Boon Leong" <boon.leong.ong@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
Sam Protsenko <semen.protsenko@linaro.org>,
Peter Jones <pjones@redhat.com>,
Andy Lutomirski <luto@amacapital.net>,
Roy Franz <roy.franz@linaro.org>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
"Fleming, Matt" <matt.fleming@intel.com>
Subject: Re: [PATCH v7 1/2] efi: export efi_capsule_supported() function symbol
Date: Wed, 07 Oct 2015 09:27:05 +0100 [thread overview]
Message-ID: <5614D759.8020405@nexus-software.ie> (raw)
In-Reply-To: <F54AEECA5E2B9541821D670476DAE19C4A864DCF@PGSMSX102.gar.corp.intel.com>
On 07/10/15 03:01, Kweh, Hock Leong wrote:
>> -----Original Message-----
>> From: Bryan O'Donoghue [mailto:pure.logic@nexus-software.ie]
>> Sent: Tuesday, October 06, 2015 10:54 PM
>>>>
>>>> Aside from that, I'm curious which types of capsules you've used here
>>>> too - does it include the MFH header ? Keep in mind the initial
>>>> firmware that shipped with Galileo will depend on that MFH being
>> present.
>>>>
>>>>
>> http://download.intel.com/support/processors/quark/sb/quark_secureboo
>>>> t
>>>> prm_330234_001.pdf
>>>> - Section A1 - table 7 ?
>>>>
>>>> So if we boot a 4.x kernel with that initial firmware version 0.75 if
>>>> memory serves - it's important that the capsule.c code handles the MFH.
>>>>
>>>
>>> Already got agreement with Matt that Quark Security Header patch will
>>> not be upstream to mainline as it is not a standard header. So Intel
>>> will carry this patch ourselves.
>>
>> Right... so what sort of capsule are you testing with ?
>
> I am testing on Intel Galileo Gen 1 with bios version v0.7.5, v0.8.0, v1.0.1 & v1.0.2.
>
> Thanks & Regards,
> Wilson
>
Hmm.
That's pretty confusing.
The 0.75 BIOS requires the MFH as far as I remember. If the capsule you
are using doesn't have the MFH - how is this working ?
next prev parent reply other threads:[~2015-10-07 8:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-05 20:15 [PATCH v7 0/2] Enable capsule loader interface for efi firmware updating Kweh, Hock Leong
2015-10-05 20:15 ` Kweh, Hock Leong
2015-10-05 20:15 ` [PATCH v7 1/2] efi: export efi_capsule_supported() function symbol Kweh, Hock Leong
2015-10-05 13:13 ` Borislav Petkov
[not found] ` <20151005131350.GA26329-K5JNixvcfoxupOikMc4+xw@public.gmane.org>
2015-10-05 15:19 ` Kweh, Hock Leong
2015-10-05 15:19 ` Kweh, Hock Leong
2015-10-05 21:27 ` Bryan O'Donoghue
[not found] ` <5612EB38.2050209-SyKdqv6vbfZdzvEItQ6vdLNAH6kLmebB@public.gmane.org>
2015-10-06 10:53 ` Kweh, Hock Leong
2015-10-06 10:53 ` Kweh, Hock Leong
[not found] ` <F54AEECA5E2B9541821D670476DAE19C4A864B5D-j2khPEwRog0FyVwBAnZdSLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-10-06 14:53 ` Bryan O'Donoghue
2015-10-06 14:53 ` Bryan O'Donoghue
[not found] ` <5613E076.20508-SyKdqv6vbfZdzvEItQ6vdLNAH6kLmebB@public.gmane.org>
2015-10-07 2:01 ` Kweh, Hock Leong
2015-10-07 2:01 ` Kweh, Hock Leong
2015-10-07 8:27 ` Bryan O'Donoghue [this message]
2015-10-10 22:02 ` Matt Fleming
2015-10-11 14:28 ` Kweh, Hock Leong
[not found] ` <F54AEECA5E2B9541821D670476DAE19C4A875128-j2khPEwRog0FyVwBAnZdSLfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-10-11 19:03 ` Matt Fleming
2015-10-11 19:03 ` Matt Fleming
[not found] ` <1444076155-19295-1-git-send-email-hock.leong.kweh-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-10-05 20:15 ` [PATCH v7 2/2] efi: a misc char interface for user to update efi firmware Kweh, Hock Leong
2015-10-05 20:15 ` Kweh, Hock Leong
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=5614D759.8020405@nexus-software.ie \
--to=pure.logic@nexus-software.ie \
--cc=James.Bottomley@hansenpartnership.com \
--cc=boon.leong.ong@intel.com \
--cc=bp@alien8.de \
--cc=gregkh@linuxfoundation.org \
--cc=hock.leong.kweh@intel.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=matt.fleming@intel.com \
--cc=matt@console-pimps.org \
--cc=pjones@redhat.com \
--cc=roy.franz@linaro.org \
--cc=semen.protsenko@linaro.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 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.