From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] configs/imx6ullevk: add imx6ullevk support
Date: Wed, 25 Sep 2019 23:17:06 +0200 [thread overview]
Message-ID: <20190925231706.4a9e92eb@windsurf> (raw)
In-Reply-To: <20190521204534.27569-1-jeffrey.kinross@i3pd.com>
Hello Jeffrey,
Thanks for your contribution, and sorry for the slow feedback. Gilles
already commented that the DEVELOPERS file needs to be updated. But
there is another issue that I can't fix myself. See below.
On Tue, 21 May 2019 15:45:34 -0500
jeffrey.kinross at i3pd.com wrote:
> +# bootloader
> +BR2_TARGET_UBOOT=y
> +BR2_TARGET_UBOOT_BOARDNAME="mx6ullevk"
This option does not exist when BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y.
> +BR2_TARGET_UBOOT_BUILD_SYSTEM_KCONFIG=y
> +BR2_TARGET_UBOOT_USE_DEFCONFIG=y
> +BR2_TARGET_UBOOT_BOARD_DEFCONFIG="mx6ull_14x14_evk"
> +BR2_TARGET_UBOOT_FORMAT_IMX=y
> +BR2_TARGET_UBOOT_NEEDS_DTC=y
But more importantly, we need to have a specific U-Boot version
selected, not just what happens to be the default. Indeed, just like
for the Linux kernel, we want to be sure to rebuild always the same
U-Boot version.
Could you adjust this, and send an updated version ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-09-25 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 20:45 [Buildroot] [PATCH 1/1] configs/imx6ullevk: add imx6ullevk support jeffrey.kinross at i3pd.com
2019-07-06 8:47 ` Gilles Talis
2019-09-25 21:17 ` Thomas Petazzoni [this message]
2019-09-26 18:14 ` [Buildroot] [PATCH v2] configs/imx6ullevk: new defconfig board/freescale/imx6ullevk/readme.txt: new readme for the imx6ullevk board. DEVELOPERS: Add myself as the maintainer of imx6ullevk Jeffrey Kinross
2020-04-13 13:53 ` Thomas Petazzoni
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=20190925231706.4a9e92eb@windsurf \
--to=thomas.petazzoni@bootlin.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