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 10:47:01 +0100 [thread overview]
Message-ID: <20191216104701.0f3af055@windsurf.home> (raw)
In-Reply-To: <1575459437-7302-1-git-send-email-eugen.hristev@microchip.com>
Hello Eugen,
On Wed, 4 Dec 2019 11:37:47 +0000
<Eugen.Hristev@microchip.com> wrote:
> diff --git a/configs/atmel_sama5d27_som1_ek_mmc_dev_defconfig b/configs/atmel_sama5d27_som1_ek_mmc_dev_defconfig
> index 1d16708..0653ae8 100644
> --- a/configs/atmel_sama5d27_som1_ek_mmc_dev_defconfig
> +++ b/configs/atmel_sama5d27_som1_ek_mmc_dev_defconfig
> @@ -70,15 +70,13 @@ BR2_TARGET_ROOTFS_EXT2=y
> BR2_TARGET_ROOTFS_EXT2_4=y
> BR2_TARGET_ROOTFS_EXT2_SIZE="120M"
> BR2_TARGET_AT91BOOTSTRAP3=y
> -BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_GIT=y
> -BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_URL="https://github.com/linux4sam/at91bootstrap.git"
> -BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_REPO_VERSION="v3.9.0"
> +BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_TARBALL=y
> +BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_TARBALL_LOCATION="(call github,linux4sam,at91bootstrap,v3.9.0)/at91bootstrap-v3.9.0.tar.gz"
In fact, there is no option BR2_TARGET_AT91BOOTSTRAP3_CUSTOM_TARBALL,
so this simply doesn't work.
I see two options:
(1) Revert back to downloading from Git
(2) Add support for the custom tarball option in
at91bootstrap3/Config.in and at91bootstrap3/at91bootstrap3.mk.
I think option (2) is the most appropriate, since we have this custom
tarball option for Linux, U-Boot, etc. already.
Could you take care of implementing this option, or should we do it ?
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-12-16 9:47 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 [this message]
2019-12-16 10:08 ` Eugen.Hristev at microchip.com
2019-12-16 10:26 ` 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=20191216104701.0f3af055@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.