Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Max Filippov <jcmvbkbc@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 6/7] linux: apply xtensa overlay
Date: Sun,  9 Jul 2017 05:22:00 -0700	[thread overview]
Message-ID: <1499602921-25097-7-git-send-email-jcmvbkbc@gmail.com> (raw)
In-Reply-To: <1499602921-25097-1-git-send-email-jcmvbkbc@gmail.com>

Xtensa core configuration must be added to linux before it can be
built for that xtensa CPU variant. Extract configuration files from the
xtensa overlay as is done for other packages that need to be configured
for a specific xtensa core.

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 makefile;
- add ARCH_XTENSA_OVERLAY_URL to EXTRA_DOWNLOADS in package makefile.

 arch/arch.mk.xtensa | 2 +-
 linux/linux.mk      | 8 ++++++++
 2 files changed, 9 insertions(+), 1 deletion(-)

diff --git a/arch/arch.mk.xtensa b/arch/arch.mk.xtensa
index ba3e3025b7d0..8841b4f9d363 100644
--- a/arch/arch.mk.xtensa
+++ b/arch/arch.mk.xtensa
@@ -23,7 +23,7 @@ endif
 # arch-xtensa-overlay-extract -- extract an extensa overlay
 #
 # argument 1 is the path in which to extract
-# argument 2 is the component to extract, one of: gcc, binutils, gdb
+# argument 2 is the component to extract, one of: gcc, binutils, gdb, linux
 #
 # Example:
 #   $(call arch-xtensa-overlay-extract,/path/to/overlay.tar,$(@D),gcc)
diff --git a/linux/linux.mk b/linux/linux.mk
index b0e974774af9..032d64fc22e3 100644
--- a/linux/linux.mk
+++ b/linux/linux.mk
@@ -86,6 +86,14 @@ ifeq ($(BR2_PACKAGE_HOST_UBOOT_TOOLS),y)
 LINUX_DEPENDENCIES += host-uboot-tools
 endif
 
+ifneq ($(ARCH_XTENSA_OVERLAY_FILE),)
+define LINUX_XTENSA_OVERLAY_EXTRACT
+	$(call arch-xtensa-overlay-extract,$(@D),linux)
+endef
+LINUX_POST_EXTRACT_HOOKS += LINUX_XTENSA_OVERLAY_EXTRACT
+LINUX_EXTRA_DOWNLOADS += $(ARCH_XTENSA_OVERLAY_URL)
+endif
+
 LINUX_MAKE_FLAGS = \
 	HOSTCC="$(HOSTCC)" \
 	HOSTCFLAGS="$(HOSTCFLAGS)" \
-- 
2.1.4

  parent reply	other threads:[~2017-07-09 12:22 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
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 ` Max Filippov [this message]
2017-07-09 12:22 ` [Buildroot] [PATCH v2 7/7] uboot: apply xtensa overlay 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=1499602921-25097-7-git-send-email-jcmvbkbc@gmail.com \
    --to=jcmvbkbc@gmail.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