[U-Boot] [PATCH v3 00/25] dm: Introduce Rockchip RK3288 support

Simon Glass
2015-06-24T17:48:04Z

Hi,

On 24 June 2015 at 11:39, Heiko St?bner <heiko@sntech.de> wrote:
> Am Mittwoch, 24. Juni 2015, 09:54:07 schrieb Kevin Hilman:
>> Simon Glass <sjg@chromium.org> writes:
>> > The Rockchip RK3288 is based on a quad-core Cortex-A17 CPU and has a good
>> > set of peripherals. Various full-featured U-Boot ports are available and
>> > this is an attempt to bring those features into mainline. With this series
>> > the Firefly RK3288 can boot to a prompt from an SD card.
>> >
>> > Since much of the code is generic, this also supports the Radxa Rock Pro.
>> > Since there is no device tree available for that yet, it uses the same
>> > config and device tree as the Firefly. This works because not all
>> > peripherals are supported, so the differences don't matter.
>> >
>> > Support for booting from USB OTG is also provided, using the on-chip boot
>> > ROM and the rkflashtool utility. This can boot as far as SPL, but there is
>> > no support for reading U-Boot proper from USB as yet. This requires
>> > implementing a suitable protocol (perhaps DFU or Rockchip's proprietary
>> > one) in SPL.
>> >
>> > Support is also provided for the Haier Chromebook, which is based on the
>> > same SoC. In this case it boots from SPI rather than an SD card.
>>
>> Any testing on the Hisense Chromebook with the same SoC? I don't know
>> if there are significant differences with the Haier one that would
>> effect this.
>
> From what I know, the jerry dts in this series actually is the Hisense
> Chromebook? Looking at the dts files you'll see that they're all actually
> pretty similar.

Yes, very similar. If you look at the board configs you'll see that
almost everything is common. The only difference is the features that
are enabled in SPL (for code size reasons at present it doesn't
support both SPI and MMC booting).

When you change out the device tree it should boot on any of the
RK3288 platforms. There is nothing hardware-specific in the
implementation or config. Everything uses driver model and device
tree.

Regards,
Simon