[U-Boot] [RFC PATCH 0/6] x86: New Intel Quark SoC support

Simon Glass sjg at chromium.org
Thu Jan 29 03:30:24 CET 2015


Hi Bin,

On 28 January 2015 at 19:27, Bin Meng <bmeng.cn at gmail.com> wrote:
> Hi Simon,
>
> On Thu, Jan 29, 2015 at 2:05 AM, Simon Glass <sjg at chromium.org> wrote:
>> Hi Bin,
>>
>> On 28 January 2015 at 07:19, Bin Meng <bmeng.cn at gmail.com> wrote:
>>> This series adds the first step of bare support for the Intel Quark
>>> SoC support which can be validated on Intel Galileo board.
>>>
>>> Intel Quark is a line of 32-bit x86 SoCs by Intel, designed for small
>>> size and low power consumption, and targeted at new markets including
>>> wearable devices. They are smaller and slower than Atom processors and
>>> consume less power. They lack support for SIMD instruction sets (such
>>> as MMX and SSE) and only support embedded operating systems. Quark
>>> powers the Intel Galileo developer microcontroller board. The CPU
>>> instruction set is the same as Pentium (P54C/i586) CPU.
>>>
>>> Intel decided to completely publish Quark's hardware specification to
>>> software developers, which includes an SoC datasheet, a UEFI Firmware
>>> Writer's Guide, and a complete reference source code for the UEFI BIOS
>>> which is pre-flahsed on the Galileo board. As of today, the only BIOS
>>> for Galileo is the Intel one with UEFI inteface only. There is no CSM
>>> support yet in that BIOS, neither any 3rd party BIOS vendor provides
>>> support to Quark SoC.
>>
>> So no binary blobs?
>
> Ah, forget to mention, only one binary blob (exactly 8KiB) is needed
> which is rmu.bin for Remote Management Unit. Not like FSP, U-Boot will
> not call into the binary. The binary is needed by the Quark SoC
> itself. Everything on Quark will have its source codes including MRC.

Someone should suggest using on-chip ROM :-)

>
>>>
>>> Note there are two generation of Galileo boards, aka gen1 and gen2.
>>> Currently the development work is on gen2, but once we get it boot,
>>> we can easily add the gen1 board (old version).
>>>
>>> With this patch series, the generated u-boot.rom could boot the Intel
>>> Galileo board up to fdt relocate, where U-Boot hangs because the DRAM
>>> is not initializaed yet. A follow up patch series will be sent soon
>>> to add support for Memory Reference Code (MRC).
>>>
>>> Note this patch series may need rebase after Simon's Minnowmax support
>>> patch series is applied.
>>
>> You can rebase on x86/minnow-working if you like.
>
> I will rebase this on u-boot-x86/master since I noticed that you have
> already applied the minnowmax patch series.

Yes it is there. Please let me know if you see any problems.

Regards,
Simon


More information about the U-Boot mailing list