Messages in this thread | | | From | Andy Shevchenko <> | Date | Wed, 1 Mar 2017 16:55:16 +0200 | Subject | Re: [PATCH 0/2] efi: Enhance capsule loader to support signed Quark images |
| |
On Wed, Mar 1, 2017 at 4:02 PM, Bryan O'Donoghue <pure.logic@nexus-software.ie> wrote:
>>> 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.
> CONFIG_SMP=y - no difference - like I say it's PF# on lock prefix > instructions, not SMP=y that's the problem here > CONFIG_M686=y (doesnt' boot) > CONFIG_M586TSC=y does boot
> So yes M686 is not bootable on this part. My point to you about having a > custom kernel though still stands, you shouldn't have to compile a quark > specific kernel - just a 586TSC kernel with Quark support.
... which is not default. That's my point.
> For example CentOS is bootable on Quark.
Because someone there took care of it. (I think being i586 compatible binaries as well)
-- With Best Regards, Andy Shevchenko
| |