[LEDE-DEV] LEDE Intel Galileo Gen 2 port

Hauke Mehrtens hauke at hauke-m.de
Mon Jan 1 16:56:49 PST 2018


On 01/01/2018 08:04 PM, perillamint wrote:
> BTW, it seems Intel Quark X1000 SoC may affected by Pentium F00F bug or
> its variant (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738575)
> 
> I wonder LEDE build system can workaround this kind of bug. It seems
> appending NOP before every LOCK instruction is required for Quark X1000
> SoC (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738575#65)

You can create a new subtarget in in the x86 target like this one:
target/linux/x86/quark/target.mk

Is there a option for gcc to workaround this problem in the Quark CPU?
If so you can create CPU_CFLAGS_quark in include/target.mk and select it
in you target.mk.

Hauke

> On 29/12/2017 14.31, perillamint wrote:
>> Hello, everyone.
>>
>> Recently I got few Galileo Gen 2 boards from Seeed studio clearance. I
>> tried to boot OpenWRT on them and successfully booted it with some hacks.
>>
>> So, I'm considering submitting patch for that after cleaning hacks into
>> proper platform support but I'm skeptical about its "usefulness" because
>> Intel discontinues Galileo and other boards. No one will be able to get
>> fresh new Galileo boards from Intel.
>>
>> Should I submit my patches to LEDE or not?
>>
>> Thanks.
>>
>> _______________________________________________
>> Lede-dev mailing list
>> Lede-dev at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/lede-dev
>>
> 
> _______________________________________________
> Lede-dev mailing list
> Lede-dev at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev
> 




More information about the Lede-dev mailing list