Skip to contentSkip to conversation

i386 machine.cfg: Explicitly disable 64BIT

PATCH In review Saul Wold 2 participants 3 messages Mar 30, 2017

lore
Share & tools
lore

Saul Wold

author
#0 lore raw

PATCH 1/1 i386 machine.cfg: Explicitly disable 64BIT

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

[YOCTO #11230]

Signed-off-by Saul Wold <[email protected]>
---
 .../substrate/target/arch/i386/recipes-kernel/linux/files/machine.cfg  | 3 +++
 1 file changed, 3 insertions(+)
scripts/lib/bsp/substrate/target/arch/i386/recipes-kernel/linux/files/machine.cfg +3 -0
index 3b168b7..fe5b882 100644
@@ -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
Signature · 1 line
2.7.4
#1 lore raw
Quoted 4 lines · Saul Wold

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.

Saul, this is poky code, so wrong list.

Quoted 25 lines

Similar to e9ec769926b2378e63380bd7762ce7ce201af151 in the yocto-kernel-cache repo

[YOCTO #11230]

Signed-off-by Saul Wold <[email protected]>
---
 .../substrate/target/arch/i386/recipes-kernel/linux/files/machine.cfg  | 3 +++
 1 file changed, 3 insertions(+)
scripts/lib/bsp/substrate/target/arch/i386/recipes-kernel/linux/files/machine.cfg +3 -0
index 3b168b7..fe5b882 100644
@@ -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
Signature · 1 line
2.7.4
author
#2 lore raw
Quoted 11 lines · Leonardo Sandoval
Quoted 8 lines · Saul Wold

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.

Quoted 2 lines

Saul, this is poky code, so wrong list.

I am just having a bad day with email!

Sau!

Quoted 37 lines
Quoted 35 lines

Similar to e9ec769926b2378e63380bd7762ce7ce201af151 in the yocto- kernel-cache repo

[YOCTO #11230]

Signed-off-by Saul Wold <[email protected]>

---
 .../substrate/target/arch/i386/recipes-
kernel/linux/files/machine.cfg  | 3 +++

 1 file changed, 3 insertions(+)
(quoted diff) +0 -0

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

scripts/lib/bsp/substrate/target/arch/i386/recipes-kernel/linux/files/machine.cfg +0 -0
@@ -1,5 +1,8 @@
  # yocto-bsp-filename {{=machine}}.cfg

 CONFIG_X86_32=y

scripts/lib/bsp/substrate/target/arch/i386/recipes-kernel/linux/files/machine.cfg +3 -0
+# Must explicitly disable 64BIT
+# CONFIG_64BIT is not set
+

 CONFIG_MATOM=y
 CONFIG_PRINTK=y

--
2.7.4