On 28/02/17 17:42, Bryan O'Donoghue wrote:
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.
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.
For example CentOS is bootable on Quark.
---
bod
--
To unsubscribe from this list: send the line "unsubscribe linux-efi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
