Skip to contentSkip to conversation

ARM: mvebu: add appended DTB support in mvebu_v5_defconfig

PATCH New Thomas Petazzoni 3 participants 5 messages Jul 3, 2014 – Jul 8, 2014

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/2 ARM: mvebu: add appended DTB support in mvebu_v5_defconfig

The mvebu_v5_defconfig is currently used for Kirkwood platforms, and in the future hopefully used for Orion5x platforms. Those platforms use fairly old bootloaders that don't have Device Tree support, so it makes sense to enable appended DTB support by default, as well as the backward compatibility with ATAGS passed by the bootloader for those platforms. It helps having a defconfig that works fine out of the box for most Kirkwood platforms.

---
 arch/arm/configs/mvebu_v5_defconfig | 2 ++
 1 file changed, 2 insertions(+)
arch/arm/configs/mvebu_v5_defconfig +2 -0
index 27c732f..9f70f59 100644
@@ -19,6 +19,8 @@ CONFIG_AEABI=y
 CONFIG_HIGHMEM=y
 CONFIG_ZBOOT_ROM_TEXT=0x0
 CONFIG_ZBOOT_ROM_BSS=0x0
+CONFIG_ARM_APPENDED_DTB=y
+CONFIG_ARM_ATAG_DTB_COMPAT=y
 CONFIG_CPU_FREQ=y
 CONFIG_CPU_FREQ_STAT_DETAILS=y
 CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
Signature · 1 line
2.0.0
#1 lore raw

PATCH 2/2 ARM: mvebu: add devtmpfs to mvebu_v5_defconfig

The devtmpfs filesystem is now widely used and generally needed to boot Linux systems. 42 ARM defconfigs have it enabled, so it makes sense to have it enabled as well in mvebu_v5_defconfig.

---
 arch/arm/configs/mvebu_v5_defconfig | 2 ++
 1 file changed, 2 insertions(+)
arch/arm/configs/mvebu_v5_defconfig +2 -0
index 9f70f59..5df35e9 100644
@@ -38,6 +38,8 @@ CONFIG_NET_PKTGEN=m
 CONFIG_CFG80211=y
 CONFIG_MAC80211=y
 CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
+CONFIG_DEVTMPFS=y
+CONFIG_DEVTMPFS_MOUNT=y
 CONFIG_MTD=y
 CONFIG_MTD_CMDLINE_PARTS=y
 CONFIG_MTD_BLOCK=y
Signature · 1 line
2.0.0
maintainer
#2 lore raw

PATCH 2/2 ARM: mvebu: add devtmpfs to mvebu_v5_defconfig

Quoted 5 lines · Thomas Petazzoni

The devtmpfs filesystem is now widely used and generally needed to boot Linux systems. 42 ARM defconfigs have it enabled, so it makes sense to have it enabled as well in mvebu_v5_defconfig.

I have Debian sid on my boxes, and they is quite happy without devtmpfs. Hence i've not proposed such a patch before.

Andrew

Quoted 20 lines
---
 arch/arm/configs/mvebu_v5_defconfig | 2 ++
 1 file changed, 2 insertions(+)
arch/arm/configs/mvebu_v5_defconfig +2 -0
index 9f70f59..5df35e9 100644
@@ -38,6 +38,8 @@ CONFIG_NET_PKTGEN=m
 CONFIG_CFG80211=y
 CONFIG_MAC80211=y
 CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
+CONFIG_DEVTMPFS=y
+CONFIG_DEVTMPFS_MOUNT=y
 CONFIG_MTD=y
 CONFIG_MTD_CMDLINE_PARTS=y
 CONFIG_MTD_BLOCK=y
Signature · 1 line
2.0.0
maintainer
#3 lore raw

PATCH 1/2 ARM: mvebu: add appended DTB support in mvebu_v5_defconfig

In reply to Thomas Petazzoni
Quoted 9 lines · Thomas Petazzoni

The mvebu_v5_defconfig is currently used for Kirkwood platforms, and in the future hopefully used for Orion5x platforms. Those platforms use fairly old bootloaders that don't have Device Tree support, so it makes sense to enable appended DTB support by default, as well as the backward compatibility with ATAGS passed by the bootloader for those platforms. It helps having a defconfig that works fine out of the box for most Kirkwood platforms.

Hi Thomas

And a minor nit. Jason would like to see kirkwood in the subject, instead of mvebu, so we have a simple way to filter patches by SoC in mvebu.

Andrew

Quoted 20 lines
---
 arch/arm/configs/mvebu_v5_defconfig | 2 ++
 1 file changed, 2 insertions(+)
arch/arm/configs/mvebu_v5_defconfig +2 -0
index 27c732f..9f70f59 100644
@@ -19,6 +19,8 @@ CONFIG_AEABI=y
 CONFIG_HIGHMEM=y
 CONFIG_ZBOOT_ROM_TEXT=0x0
 CONFIG_ZBOOT_ROM_BSS=0x0
+CONFIG_ARM_APPENDED_DTB=y
+CONFIG_ARM_ATAG_DTB_COMPAT=y
 CONFIG_CPU_FREQ=y
 CONFIG_CPU_FREQ_STAT_DETAILS=y
 CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
Signature · 1 line
2.0.0
#4 lore raw

PATCH 1/2 ARM: mvebu: add appended DTB support in mvebu_v5_defconfig

In reply to Thomas Petazzoni

Thomas,

Quoted 8 lines · Thomas Petazzoni

The mvebu_v5_defconfig is currently used for Kirkwood platforms, and in the future hopefully used for Orion5x platforms. Those platforms use fairly old bootloaders that don't have Device Tree support, so it makes sense to enable appended DTB support by default, as well as the backward compatibility with ATAGS passed by the bootloader for those platforms. It helps having a defconfig that works fine out of the box for most Kirkwood platforms.

Quoted 4 lines
---
 arch/arm/configs/mvebu_v5_defconfig | 2 ++
 1 file changed, 2 insertions(+)

Both applied to mvebu/defconfig with Andrew's Ack.

thx,

Jason.