[U-Boot] [PATCH v1 16/16] board: Add Qualcomm Dragonboard 410C support

[Mateusz Kulikowski]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi (again),

On 20.01.2016 05:35, Simon Glass wrote:
> On 6 January 2016 at 11:21, Mateusz Kulikowski
> <mateusz.kulikowski at gmail.com> wrote:

> 
> Can you please add a MAINTAINERS file also?
Of course, 

I will also add myself somewhere as a maintainer for SPMI/SoC and all the drivers that I did
(at least if it will be possible).

> 
> Tested-by: Simon Glass <sjg at chromium.org>

Great! 

>> +       .quad   0                               // reserved
>> +       .quad   0                               // reserved
>> +       .quad   0                               // reserved
>> +       .byte   0x41                            // Magic number, "ARM\x64"
>> +       .byte   0x52
>> +       .byte   0x4d
>> +       .byte   0x64
>> +       .word   0                               // reserved
>> diff --git a/board/qualcomm/dragonboard410c/readme.txt b/board/qualcomm/dragonboard410c/readme.txt
>> new file mode 100644
>> index 0000000..0f575db
>> --- /dev/null
>> +++ b/board/qualcomm/dragonboard410c/readme.txt
>> @@ -0,0 +1,40 @@
>> +#
>> +# (C) Copyright 2015 Mateusz Kulikowski <mateusz.kulikowski at gmail.com>
>> +#
>> +# SPDX-License-Identifier:     GPL-2.0+
>> +#
>> +
>> +Build & Run instructions:
>> +
>> +1) Install mkbootimg from git://codeaurora.org/quic/kernel/skales (15ece94f09 worked for me)
>> +2) Setup CROSS_COMPILE to aarch64 compiler
>> +3) make dragonboard410c_config
>> +4) make
>> +5) generate fake, empty ramdisk (can have 0 bytes)
>> +$ touch rd
>> +
>> +6) generate qualcomm device tree, use dtbTool to generate it
>> +$ dtbTool -o dt.img arch/arm/dts
> 
> What is this file?

This tool that packs device tree into some proprietary (qcom) format.

Both (with ramdisk) must be in boot image (below) otherwise Little Kernel will refuse to load it.

It seems (although I'm not an Android guy) Litlle Kernel is unable to accept the fact that 
kernel image may not need ramdisk (or device tree).

> 
>> +
>> +7) generate image with mkbootimg:
>> +$ mkbootimg --kernel=u-boot-dtb.bin --output=u-boot.img --dt=dt.img  --pagesize 2048 --base 0x80000000 --ramdisk=rd --cmdline=""
> 
> Is it possible to add this functionality to mkimage? Is this building
> a fastboot image?

Yes, it's building fastboot/Android image; It even adds nice "ANDROID!" string in binary.

It probably can be added to u-boot build system, but I'm not sure if we really want it -
at least for the dragonboard my goal is to get rid of Little Kernel.


Regards,
Mateusz

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWoANoAAoJELvtohmVtQzBH6wH/2eRPDryFshrkshRoH9R7GZg
qoFk4UbHoSIh8+JpD2OsHAJI6SBao9Z/0bzdTm+7gLU7+tf8pYeU32/fzFGBjRCo
Tvm/mBMJaz55SRWWdAdeNaCQEO/cG+B2PuZeZTur0buiJymDdQ8QeIEz2Treah1P
CJ1XTsKWBdlJWjkQYnZ+JYTS4nlolK0P0FIVNavWEYtlgVmOidJRBJLFMjJ8dGaa
VhR/W1/hboTFN6QBwiBuo/36jX2Sobj4HJ1VHJ/hvNH3QzBtG+n/64Gi5bctPrWp
LKyuq0ZA15z1PquG9XrhYc8LoYgJyvfQhTAPh4cPn5zRPme/SMeIxAsQ5BR1U0s=
=1PpF
-----END PGP SIGNATURE-----