From: Max Filippov <jcmvbkbc@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] linux: add xtensa overlay unpacking to prepatch step
Date: Sun, 25 Dec 2016 05:50:37 -0800 [thread overview]
Message-ID: <1482673838-24567-2-git-send-email-jcmvbkbc@gmail.com> (raw)
In-Reply-To: <1482673838-24567-1-git-send-email-jcmvbkbc@gmail.com>
Xtensa core configuration must to be added to linux before it can be
built for that xtensa CPU variant. Extract configuration files from the
xtensa overlay in prepatch step as is done with other packages that
need to be configured for a specific xtensa core.
Signed-off-by: Max Filippov <jcmvbkbc@gmail.com>
---
linux/linux.mk | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/linux/linux.mk b/linux/linux.mk
index 988427c..f874f5e 100644
--- a/linux/linux.mk
+++ b/linux/linux.mk
@@ -82,6 +82,16 @@ ifeq ($(BR2_LINUX_KERNEL_UBOOT_IMAGE),y)
LINUX_DEPENDENCIES += host-uboot-tools
endif
+XTENSA_CORE_NAME = $(call qstrip, $(BR2_XTENSA_CORE_NAME))
+ifneq ($(XTENSA_CORE_NAME),)
+define LINUX_XTENSA_PRE_PATCH
+ test -d $(@D)/arch/xtensa/variants/$(XTENSA_CORE_NAME) || \
+ tar xf $(BR2_XTENSA_OVERLAY_DIR)/xtensa_$(XTENSA_CORE_NAME).tar \
+ -C $(@D) --strip-components=1 linux
+endef
+LINUX_PRE_PATCH_HOOKS += LINUX_XTENSA_PRE_PATCH
+endif
+
LINUX_MAKE_FLAGS = \
HOSTCC="$(HOSTCC)" \
HOSTCFLAGS="$(HOSTCFLAGS)" \
--
2.1.4
next prev parent reply other threads:[~2016-12-25 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-25 13:50 [Buildroot] [PATCH 0/2] add custom xtensa core support to linux and U-Boot Max Filippov
2016-12-25 13:50 ` Max Filippov [this message]
2016-12-25 13:50 ` [Buildroot] [PATCH 2/2] uboot: add xtensa overlay unpacking to prepatch step Max Filippov
2017-01-06 19:52 ` [Buildroot] [PATCH 0/2] add custom xtensa core support to linux and U-Boot Max Filippov
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=1482673838-24567-2-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