[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ce0ddedb-ee72-8dba-0e60-8d5e2d7a69a0@nexus-software.ie>
Date: Tue, 28 Feb 2017 17:42:25 +0000
From: Bryan O'Donoghue <pure.logic@...us-software.ie>
To: Andy Shevchenko <andy.shevchenko@...il.com>
Cc: Ard Biesheuvel <ard.biesheuvel@...aro.org>,
Matt Fleming <matt@...eblueprint.co.uk>,
Jan Kiszka <jan.kiszka@...mens.com>,
"Kweh, Hock Leong" <hock.leong.kweh@...el.com>,
"linux-efi@...r.kernel.org" <linux-efi@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Borislav Petkov <bp@...en8.de>,
"Ong, Boon Leong" <boon.leong.ong@...el.com>,
"Mok, Tze Siong" <tze.siong.mok@...el.com>
Subject: Re: [PATCH 0/2] efi: Enhance capsule loader to support signed Quark
images
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
Powered by blists - more mailing lists