Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/7] arch/xtensa: allow specifying path to tarball file
Date: Sun, 9 Jul 2017 15:45:16 +0200	[thread overview]
Message-ID: <20170709154516.1e95e778@windsurf> (raw)
In-Reply-To: <1499602921-25097-3-git-send-email-jcmvbkbc@gmail.com>

Hello,

On Sun,  9 Jul 2017 05:21:56 -0700, Max Filippov wrote:
> From: "Yann E. MORIN" <yann.morin.1998@free.fr>
> 
> currently, specifying a custom Xtrensa core is done with two variables:
>   - the core name
>   - the directory containing the overlay tarball
> 
> However, the core name only serves to construct the tarball name, and is
> not used whatsoever to configure any of the toolchain components
> (binutils, gcc or gdb), except through the files that are overlayed in
> their respective source trees.
> 
> This has two main drawbacks:
>   - the overlay file must be named after the core,
>   - the tarball can not be compressed.
> 
> Furthermore, it also makes it extremely complex to implement a download
> of that tarball.
> 
> So, those two variables can be squeezed into a single variable, that is
> the complete path of the overlay tarball.
> 
> Update the qemu-xtensa defconfig accordingly.
> 
> Note: we do not add a legacy entry for BR2_XTENSA_CORE_NAME, since it
> was previously a blind option in the last release, and there's been no
> release since we removed BR2_XTENSA_CUSTOM_NAME. So, we just update the
> legacy comments for BR2_XTENSA_CUSTOM_NAME, since that's all the user
> could have seen in any of our releases so far.
> 
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
> ---
> Changes v1->v2:
> - replace ARCH_XTENSA_CORE_NAME with ARCH_XTENSA_OVERLAY_FILE in overlay
>   application conditions in package makefiles.

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2017-07-09 13:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-09 12:21 [Buildroot] [PATCH v2 0/7] xtensa overlay application rework Max Filippov
2017-07-09 12:21 ` [Buildroot] [PATCH v2 1/7] arch/xtensa: get rid of an intermediate blind kconfig option Max Filippov
2017-07-09 13:45   ` Thomas Petazzoni
2017-07-09 12:21 ` [Buildroot] [PATCH v2 2/7] arch/xtensa: allow specifying path to tarball file Max Filippov
2017-07-09 13:45   ` Thomas Petazzoni [this message]
2017-07-09 12:21 ` [Buildroot] [PATCH v2 3/7] arch/xtensa: accept the overlay to be compressed Max Filippov
2017-07-09 13:45   ` Thomas Petazzoni
2017-07-09 12:21 ` [Buildroot] [PATCH v2 4/7] arch/xtensa: accept the overlay to be an URL Max Filippov
2017-07-09 13:48   ` Thomas Petazzoni
2017-07-09 13:57     ` Yann E. MORIN
2017-07-09 15:24       ` Thomas Petazzoni
2017-07-09 12:21 ` [Buildroot] [PATCH v2 5/7] configs/qemu-xtensa: use overlay from the github repository Max Filippov
2017-07-09 12:22 ` [Buildroot] [PATCH v2 6/7] linux: apply xtensa overlay Max Filippov
2017-07-09 12:22 ` [Buildroot] [PATCH v2 7/7] uboot: " Max Filippov
2017-07-09 15:22 ` [Buildroot] [PATCH v2 0/7] xtensa overlay application rework 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=20170709154516.1e95e778@windsurf \
    --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