From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs: add nitrogen6sx_defconfig for Boundary Devices SoloX board
Date: Mon, 21 Sep 2015 20:08:16 +0300 [thread overview]
Message-ID: <20150921170816.GC2242@tarshish> (raw)
In-Reply-To: <CAAMH-yt8Y3GruOxEvw9op=-00op9pnVA_L0ddwi1XNT3b1qqwA@mail.gmail.com>
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@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
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2015-09-21 17:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-11 10:00 [Buildroot] [PATCH] configs: add nitrogen6sx_defconfig for Boundary Devices SoloX board Gary Bisson
2015-09-19 13:34 ` Thomas Petazzoni
2015-09-21 16:19 ` Gary Bisson
2015-09-21 17:08 ` Baruch Siach [this message]
2015-09-21 17:27 ` Gary Bisson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150921170816.GC2242@tarshish \
--to=baruch@tkos.co.il \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox