From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] configs/atmel: update u-boot-at91 and bootstrap to tarballs
Date: Mon, 16 Dec 2019 11:26:54 +0100 [thread overview]
Message-ID: <20191216112654.41dcdde1@windsurf.home> (raw)
In-Reply-To: <d849cb07-7c68-2b63-d44e-4a93c45e3d88@microchip.com>
On Mon, 16 Dec 2019 10:08:55 +0000
<Eugen.Hristev@microchip.com> wrote:
> I can help doing it. Here is a quick work , is it okay? send a patch ?
> or there is more to do this than simply what I did below:
You certainly also need some changes in the Config.in file. I recommend
testing your changes before sending them :-)
Also, the patch snippet below was line-wrapped by your e-mail client,
so it's not easy to review.
> diff --git a/boot/at91bootstrap3/at91bootstrap3.mk
> b/boot/at91bootstrap3/at91bootstrap3.mk
> index 685be5b..a491aaf 100644
> --- a/boot/at91bootstrap3/at91bootstrap3.mk
> +++ b/boot/at91bootstrap3/at91bootstrap3.mk
> @@ -6,7 +6,12 @@
>
> AT91BOOTSTRAP3_VERSION = $(call
> qstrip,$(BR2_TARGET_AT91BOOTSTRAP3_VERSION))
>
> -ifeq ($(BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_GIT),y)
> +ifeq ($(AT91BOOTSTRAP_VERSION),custom)
Should be:
ifeq ($(BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_TARBALL),y)
> +# Handle custom AT91Bootstrap tarballs as specified by the configuration
> +AT91BOOTSTRAP_TARBALL = $(call
> qstrip,$(BR2_TARGET_AT91BOOTSTRAP_CUSTOM_TARBALL_LOCATION))
> +AT91BOOTSTRAP_SITE = $(patsubst %/,%,$(dir $(AT91BOOTSTRAP_TARBALL)))
> +AT91BOOTSTRAP_SOURCE = $(notdir $(AT91BOOTSTRAP_TARBALL))
> +else ifeq ($(BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_GIT),y)
> AT91BOOTSTRAP3_SITE = $(call
> qstrip,$(BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_URL))
> AT91BOOTSTRAP3_SITE_METHOD = git
> BR_NO_CHECK_HASH_FOR += $(AT91BOOTSTRAP3_SOURCE)
> @@ -54,6 +59,15 @@ AT91BOOTSTRAP3_KCONFIG_OPTS = $(AT91BOOTSTRAP3_MAKE_OPTS)
> # Must be before we call to kconfig-package
> ifeq ($(BR_BUILDING),y)
>
> +#
> +# Check custom tarball option
> +#
> +ifeq ($(BR2_TARGET_AT91BOOTSTRAP_CUSTOM_TARBALL),y)
> +ifeq ($(call qstrip,$(BR2_TARGET_AT91BOOTSTRAP_CUSTOM_TARBALL_LOCATION)),)
> +$(error No custom AT91Bootstrap tarball specified. Check your
> BR2_TARGET_AT91BOOTSTRAP_CUSTOM_TARBALL_LOCATION setting)
> +endif # qstrip BR2_TARGET_AT91BOOTSTRAP_CUSTOM_TARBALL_LOCATION
> +endif # BR2_TARGET_AT91BOOTSTAP_CUSTOM_TARBALL
Otherwise, it seems OK.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-12-16 10:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 11:37 [Buildroot] [PATCH v3] configs/atmel: update u-boot-at91 and bootstrap to tarballs Eugen.Hristev at microchip.com
2019-12-05 21:54 ` Thomas Petazzoni
2019-12-16 9:47 ` Thomas Petazzoni
2019-12-16 10:08 ` Eugen.Hristev at microchip.com
2019-12-16 10:26 ` Thomas Petazzoni [this message]
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=20191216112654.41dcdde1@windsurf.home \
--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