From: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Matt Fleming <matt@codeblueprint.co.uk>,
Jan Kiszka <jan.kiszka@siemens.com>,
"Kweh, Hock Leong" <hock.leong.kweh@intel.com>,
"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@alien8.de>,
"Ong, Boon Leong" <boon.leong.ong@intel.com>,
"Mok, Tze Siong" <tze.siong.mok@intel.com>
Subject: Re: [PATCH 0/2] efi: Enhance capsule loader to support signed Quark images
Date: Tue, 28 Feb 2017 17:42:25 +0000 [thread overview]
Message-ID: <ce0ddedb-ee72-8dba-0e60-8d5e2d7a69a0@nexus-software.ie> (raw)
In-Reply-To: <CAHp75VdELFFeoJXXHbsHHuyd2xBY0y4T+M7q5+ZFN=ep3Qy9HQ@mail.gmail.com>
On 28/02/17 17:18, Andy Shevchenko wrote:
> On Tue, Feb 28, 2017 at 6:52 PM, Bryan O'Donoghue
>> A kernel compiled like this
>>
>> make menuconfig ARCH=i386
>
> I hope you care that it is equivalent to
>
> make menuconfig ARCH=i686
>
>> make bzImage -j 8
>>
>> will run just fine on Quark x1000 I do it regularly. CPUID ought to (and
>> does) inform the runtime kernel of what to do re: MSRs etc.
>>
>> We won't execute xmm/mmx, we won't touch 686 specific MSRs etc, etc.
>
> It is i*6*86 code still.
>
> So, summarize, you state that
> 1. CONFIG_SMP=y and
> 2. CONFIG_M686=y and
> 3. Kernel works on Quark
>
> Is it correct?
Logically yes. It's a very long time since I looked in detail. No harm
in checking it out though.
I'll compile up the above kernel this evening (GMT) and verify.
--
bod
next prev parent reply other threads:[~2017-02-28 18:44 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-15 18:14 Jan Kiszka
2017-02-15 18:14 ` [PATCH 1/2] efi/capsule: Prepare for loading images with security header Jan Kiszka
2017-02-15 18:14 ` [PATCH 2/2] efi/capsule: Add support for Quark " Jan Kiszka
2017-02-17 1:30 ` Bryan O'Donoghue
2017-03-24 16:44 ` Jan Kiszka
2017-02-15 18:17 ` [PATCH 0/2] efi: Enhance capsule loader to support signed Quark images Ard Biesheuvel
2017-02-15 18:47 ` Jan Kiszka
2017-02-15 18:41 ` Andy Shevchenko
2017-02-15 18:46 ` Andy Shevchenko
2017-02-15 18:50 ` Jan Kiszka
2017-02-15 18:59 ` Jan Kiszka
2017-02-16 3:00 ` Kweh, Hock Leong
2017-02-16 7:29 ` Jan Kiszka
2017-02-18 21:48 ` Ard Biesheuvel
2017-02-19 13:33 ` Jan Kiszka
2017-02-20 1:33 ` Bryan O'Donoghue
2017-02-20 1:52 ` Jan Kiszka
2017-03-24 15:18 ` Jan Kiszka
2017-02-17 0:53 ` Bryan O'Donoghue
2017-02-17 8:23 ` Kweh, Hock Leong
2017-02-17 9:24 ` Jan Kiszka
2017-02-28 12:12 ` Matt Fleming
2017-02-28 12:20 ` Jan Kiszka
2017-02-28 12:29 ` Matt Fleming
2017-02-28 13:25 ` Ard Biesheuvel
2017-02-28 13:35 ` Andy Shevchenko
2017-02-28 13:36 ` Andy Shevchenko
2017-02-28 15:07 ` Bryan O'Donoghue
2017-02-28 15:09 ` Bryan O'Donoghue
2017-02-28 15:27 ` Andy Shevchenko
2017-02-28 16:52 ` Bryan O'Donoghue
2017-02-28 17:18 ` Andy Shevchenko
2017-02-28 17:42 ` Bryan O'Donoghue [this message]
2017-03-01 14:02 ` Bryan O'Donoghue
2017-03-01 14:55 ` Andy Shevchenko
2017-02-17 9:51 ` Bryan O'Donoghue
2017-02-17 10:14 ` Jan Kiszka
2017-02-17 11:42 ` Bryan O'Donoghue
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=ce0ddedb-ee72-8dba-0e60-8d5e2d7a69a0@nexus-software.ie \
--to=pure.logic@nexus-software.ie \
--cc=andy.shevchenko@gmail.com \
--cc=ard.biesheuvel@linaro.org \
--cc=boon.leong.ong@intel.com \
--cc=bp@alien8.de \
--cc=hock.leong.kweh@intel.com \
--cc=jan.kiszka@siemens.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=tze.siong.mok@intel.com \
/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
all inboxes | Powered by JetHome®