[Buildroot] [PATCH] configs: add nitrogen6sx_defconfig for Boundary Devices SoloX board

Gary Bisson gary.bisson at boundarydevices.com
Mon Sep 21 17:27:41 UTC 2015


Hi Baruch,

On Mon, Sep 21, 2015 at 7:08 PM, Baruch Siach <baruch at tkos.co.il> wrote:
> Hi Gary,
>
> On Mon, Sep 21, 2015 at 06:19:03PM +0200, Gary Bisson wrote:
>> On Sat, Sep 19, 2015 at 3:34 PM, Thomas Petazzoni
>> <thomas.petazzoni at free-electrons.com> wrote:
>> > On Fri, 11 Sep 2015 12:00:09 +0200, Gary Bisson wrote:
>> >> This board is using the exact same kernel and u-boot revision as the
>> >> Nitrogen6x. They also share the same u-boot "autoboot" script.
>> >>
>> >> The differences between the two configurations are:
>> >> - getty port is ttymxc0 instead of ttymxc1
>> >> - uImage load address is 0x80008000
>> >
>> > Do you have a reason to keep using uImage instead of using zImage?
>> > uImage are now a bit deprecated on ARM, and zImage is the modern way of
>> > booting the kernel even from U-Boot (using the bootz command).
>>
>> Legacy I guess. I should look into it but the main advantage I see of
>> bootm/uImage is the CRC check. What is the story behind the switch to
>> bootz?
>
> Multiplatform. See [1], for example.
>
> [1]
> http://lists.infradead.org/pipermail/linux-arm-kernel/2011-September/066289.html

Thanks for the link. So indeed the mx6qdl vs mx6sx is the perfect
example to show the need of bootz.

Thanks,
Gary



More information about the buildroot mailing list