From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] configs: add nitrogen6sx_defconfig for Boundary Devices SoloX board
Date: Sat, 19 Sep 2015 15:34:10 +0200 [thread overview]
Message-ID: <20150919153410.06fe7394@free-electrons.com> (raw)
In-Reply-To: <1441965609-4092-1-git-send-email-gary.bisson@boundarydevices.com>
Gary,
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).
> I didn't include this patch as part of the Freescale packages update
> as it is an addition. However this patch depends on the updates to be
> applied for graphics support and so on.
> http://lists.busybox.net/pipermail/buildroot/2015-September/139278.html
No problem, I applied them already.
> I wish we could do an include of another defconfig, that'd simplify
> future config updates as it could look like:
>
> include nitrogen6x_defconfig
> BR2_TARGET_GENERIC_GETTY_PORT="ttymxc0"
> BR2_LINUX_KERNEL_UIMAGE_LOADADDR="0x80008000"
> BR2_LINUX_KERNEL_INTREE_DTS_NAME="imx6sx-nitrogen6sx"
>
> That would also be very useful for all the Freescale sabre boards
> where every config is almost the same apart from uboot configuration
> or device tree name.
Indeed. We don't have a solution for this in the upstream Buildroot.
However, people in this situation are encouraged to use the concept of
"defconfig" fragments, which can be merged together to give the final
defconfig.
I've applied your patch.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-09-19 13:34 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 [this message]
2015-09-21 16:19 ` Gary Bisson
2015-09-21 17:08 ` Baruch Siach
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=20150919153410.06fe7394@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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