From: Saul Wold <sgw@linux.intel.com>
To: openembedded-core@lists.openembedded.org,
richard.purdie@linuxfoundation.org
Cc: bruce.ashfield@windriver.com
Subject: [PATCH] i386 machine.cfg: Explicitly disable 64BIT
Date: Thu, 30 Mar 2017 09:27:46 -0700 [thread overview]
Message-ID: <1490891266-8602-1-git-send-email-sgw@linux.intel.com> (raw)
Since we do not set the 64 bit flags, newer kernels seem to build 64bit
config files by default. This is due to a hard-coded uname -m check that
selects the KBUILD_DEFCONFIG based on the host, not the cross target.
Similar to e9ec769926b2378e63380bd7762ce7ce201af151 in the yocto-kernel-cache repo
Signed-off-by: Saul Wold <sgw@linux.intel.com>
---
.../substrate/target/arch/i386/recipes-kernel/linux/files/machine.cfg | 3 +++
1 file changed, 3 insertions(+)
diff --git a/scripts/lib/bsp/substrate/target/arch/i386/recipes-kernel/linux/files/machine.cfg b/scripts/lib/bsp/substrate/target/arch/i386/recipes-kernel/linux/files/machine.cfg
index 3b168b7..fe5b882 100644
--- a/scripts/lib/bsp/substrate/target/arch/i386/recipes-kernel/linux/files/machine.cfg
+++ b/scripts/lib/bsp/substrate/target/arch/i386/recipes-kernel/linux/files/machine.cfg
@@ -1,5 +1,8 @@
# yocto-bsp-filename {{=machine}}.cfg
CONFIG_X86_32=y
+# Must explicitly disable 64BIT
+# CONFIG_64BIT is not set
+
CONFIG_MATOM=y
CONFIG_PRINTK=y
--
2.7.4
next reply other threads:[~2017-03-30 16:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 16:27 Saul Wold [this message]
2017-03-30 16:32 ` ✗ patchtest: failure for i386 machine.cfg: Explicitly disable 64BIT Patchwork
-- strict thread matches above, loose matches on Subject: below --
2017-03-30 16:56 [PATCH] " Saul Wold
2017-03-30 17:14 ` Leonardo Sandoval
2017-03-30 17:38 ` Saul Wold
2017-03-30 17:38 Saul Wold
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=1490891266-8602-1-git-send-email-sgw@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=bruce.ashfield@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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.