* [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
@ 2013-04-04 3:29 ` Simon Horman
0 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-04 3:29 UTC (permalink / raw)
To: linux-arm-kernel
Hi,
this is a first pass at consolidating the defconfigs of shmobile.
It covers the mackerel, amradillo800eva and kzm9d boards which meet
the following criteria:
* Have the same base memory address (0x40000000).
* Work with RUNTIME_PM, it is desirable to have that a common defconfig
* Are booted via DT, enabling the command line to be supplied in the dts.
This is important to allow serial console and early printk settings,
which vary wildly between boards, to be supplied.
* Boards I have to test.
This didn't eliminate any candidates that met the above criteria.
I believe it should also be possible to add support for the APE6EVM
board to the consolidated defconfig once problems with RUNTIME_PM
have been isolated and resolved. I have send an email about this
in a separate thread "APE6EVM and Runtime PM".
I believe it may be possible to add support for the lager board
to the consolidated defconfig once I am able to bring that board up,
which should be rather soon. The lager board does not currently
have a defconfig.
Morimoto-san, I suspect it may be possible to add support for the
bockw board to the consolidated defconfig if its boot loader supports
booting using a zImage. In this case even though the base memory address
is not the same as the boards above it should be possible to specify
the base address from the boot loader. As I do not have a bockw board
I am wondering if you could investigate this.
Simon Horman (7):
ARM: shmobile: prune defconfig
ARM: shmobile: make defconfig canonical
ARM: shmobile: Add kzm9d to consolidated defconfig
ARM: shmobile: Add mackerel to consolidated defconfig
ARM: shmobile: defconfig: Remove armadillo800eva defconfig
ARM: shmobile: defconfig: Remove kzm9d defconfig
ARM: shmobile: defconfig: Remove mackerel defconfig
arch/arm/configs/armadillo800eva_defconfig | 153 ---------------------------
arch/arm/configs/kzm9d_defconfig | 88 ----------------
arch/arm/configs/mackerel_defconfig | 156 ----------------------------
arch/arm/configs/shmobile_defconfig | 51 +++++----
4 files changed, 28 insertions(+), 420 deletions(-)
delete mode 100644 arch/arm/configs/armadillo800eva_defconfig
delete mode 100644 arch/arm/configs/kzm9d_defconfig
delete mode 100644 arch/arm/configs/mackerel_defconfig
--
1.7.10.4
^ permalink raw reply [flat|nested] 38+ messages in thread
* [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
@ 2013-04-04 3:29 ` Simon Horman
0 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-04 3:29 UTC (permalink / raw)
To: linux-arm-kernel
Hi,
this is a first pass at consolidating the defconfigs of shmobile.
It covers the mackerel, amradillo800eva and kzm9d boards which meet
the following criteria:
* Have the same base memory address (0x40000000).
* Work with RUNTIME_PM, it is desirable to have that a common defconfig
* Are booted via DT, enabling the command line to be supplied in the dts.
This is important to allow serial console and early printk settings,
which vary wildly between boards, to be supplied.
* Boards I have to test.
This didn't eliminate any candidates that met the above criteria.
I believe it should also be possible to add support for the APE6EVM
board to the consolidated defconfig once problems with RUNTIME_PM
have been isolated and resolved. I have send an email about this
in a separate thread "APE6EVM and Runtime PM".
I believe it may be possible to add support for the lager board
to the consolidated defconfig once I am able to bring that board up,
which should be rather soon. The lager board does not currently
have a defconfig.
Morimoto-san, I suspect it may be possible to add support for the
bockw board to the consolidated defconfig if its boot loader supports
booting using a zImage. In this case even though the base memory address
is not the same as the boards above it should be possible to specify
the base address from the boot loader. As I do not have a bockw board
I am wondering if you could investigate this.
Simon Horman (7):
ARM: shmobile: prune defconfig
ARM: shmobile: make defconfig canonical
ARM: shmobile: Add kzm9d to consolidated defconfig
ARM: shmobile: Add mackerel to consolidated defconfig
ARM: shmobile: defconfig: Remove armadillo800eva defconfig
ARM: shmobile: defconfig: Remove kzm9d defconfig
ARM: shmobile: defconfig: Remove mackerel defconfig
arch/arm/configs/armadillo800eva_defconfig | 153 ---------------------------
arch/arm/configs/kzm9d_defconfig | 88 ----------------
arch/arm/configs/mackerel_defconfig | 156 ----------------------------
arch/arm/configs/shmobile_defconfig | 51 +++++----
4 files changed, 28 insertions(+), 420 deletions(-)
delete mode 100644 arch/arm/configs/armadillo800eva_defconfig
delete mode 100644 arch/arm/configs/kzm9d_defconfig
delete mode 100644 arch/arm/configs/mackerel_defconfig
--
1.7.10.4
^ permalink raw reply [flat|nested] 38+ messages in thread
* [RFC/PATCH 1/7] ARM: shmobile: prune defconfig
2013-04-04 3:29 ` Simon Horman
@ 2013-04-04 3:29 ` Simon Horman
-1 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-04 3:29 UTC (permalink / raw)
To: linux-arm-kernel
Remove a number of lines from the shmobile defconfig as they seem to
be orthogonal to shmobile, not necessary for booting boards,
and as far as I know not present in a number of the shmobile
board defconfigs.
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
arch/arm/configs/shmobile_defconfig | 12 ------------
1 file changed, 12 deletions(-)
diff --git a/arch/arm/configs/shmobile_defconfig b/arch/arm/configs/shmobile_defconfig
index 0f2d80d..90f5600 100644
--- a/arch/arm/configs/shmobile_defconfig
+++ b/arch/arm/configs/shmobile_defconfig
@@ -3,15 +3,9 @@ CONFIG_SYSVIPC=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT\x16
-# CONFIG_UTS_NS is not set
-# CONFIG_IPC_NS is not set
-# CONFIG_PID_NS is not set
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_PERF_EVENTS=y
CONFIG_SLAB=y
-CONFIG_MODULES=y
-CONFIG_MODULE_UNLOAD=y
-CONFIG_MODULE_FORCE_UNLOAD=y
# CONFIG_BLK_DEV_BSG is not set
# CONFIG_IOSCHED_DEADLINE is not set
# CONFIG_IOSCHED_CFQ is not set
@@ -145,9 +139,3 @@ CONFIG_NLS_ISO8859_1=y
# CONFIG_ENABLE_WARN_DEPRECATED is not set
# CONFIG_ENABLE_MUST_CHECK is not set
# CONFIG_ARM_UNWIND is not set
-CONFIG_CRYPTO=y
-CONFIG_CRYPTO_CBC=y
-CONFIG_CRYPTO_MD5=y
-CONFIG_CRYPTO_DES=y
-CONFIG_CRYPTO_ANSI_CPRNG=y
-CONFIG_XZ_DEC=y
--
1.7.10.4
^ permalink raw reply related [flat|nested] 38+ messages in thread
* [RFC/PATCH 1/7] ARM: shmobile: prune defconfig
@ 2013-04-04 3:29 ` Simon Horman
0 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-04 3:29 UTC (permalink / raw)
To: linux-arm-kernel
Remove a number of lines from the shmobile defconfig as they seem to
be orthogonal to shmobile, not necessary for booting boards,
and as far as I know not present in a number of the shmobile
board defconfigs.
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
arch/arm/configs/shmobile_defconfig | 12 ------------
1 file changed, 12 deletions(-)
diff --git a/arch/arm/configs/shmobile_defconfig b/arch/arm/configs/shmobile_defconfig
index 0f2d80d..90f5600 100644
--- a/arch/arm/configs/shmobile_defconfig
+++ b/arch/arm/configs/shmobile_defconfig
@@ -3,15 +3,9 @@ CONFIG_SYSVIPC=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=16
-# CONFIG_UTS_NS is not set
-# CONFIG_IPC_NS is not set
-# CONFIG_PID_NS is not set
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
CONFIG_PERF_EVENTS=y
CONFIG_SLAB=y
-CONFIG_MODULES=y
-CONFIG_MODULE_UNLOAD=y
-CONFIG_MODULE_FORCE_UNLOAD=y
# CONFIG_BLK_DEV_BSG is not set
# CONFIG_IOSCHED_DEADLINE is not set
# CONFIG_IOSCHED_CFQ is not set
@@ -145,9 +139,3 @@ CONFIG_NLS_ISO8859_1=y
# CONFIG_ENABLE_WARN_DEPRECATED is not set
# CONFIG_ENABLE_MUST_CHECK is not set
# CONFIG_ARM_UNWIND is not set
-CONFIG_CRYPTO=y
-CONFIG_CRYPTO_CBC=y
-CONFIG_CRYPTO_MD5=y
-CONFIG_CRYPTO_DES=y
-CONFIG_CRYPTO_ANSI_CPRNG=y
-CONFIG_XZ_DEC=y
--
1.7.10.4
^ permalink raw reply related [flat|nested] 38+ messages in thread
* [RFC/PATCH 2/7] ARM: shmobile: make defconfig canonical
2013-04-04 3:29 ` Simon Horman
@ 2013-04-04 3:29 ` Simon Horman
-1 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-04 3:29 UTC (permalink / raw)
To: linux-arm-kernel
Use make savedefconfig to update the defconfig to the current
canonical form.
This is to aid the process of adding support for other boards.
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
arch/arm/configs/shmobile_defconfig | 11 ++---------
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git a/arch/arm/configs/shmobile_defconfig b/arch/arm/configs/shmobile_defconfig
index 90f5600..fd1c074 100644
--- a/arch/arm/configs/shmobile_defconfig
+++ b/arch/arm/configs/shmobile_defconfig
@@ -1,4 +1,3 @@
-CONFIG_EXPERIMENTAL=y
CONFIG_SYSVIPC=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
@@ -13,8 +12,6 @@ CONFIG_ARCH_SHMOBILE=y
CONFIG_ARCH_R8A7740=y
CONFIG_MACH_ARMADILLO800EVA=y
# CONFIG_SH_TIMER_TMU is not set
-CONFIG_ARM_THUMB=y
-CONFIG_CACHE_L2X0=y
CONFIG_ARM_ERRATA_430973=y
CONFIG_ARM_ERRATA_458693=y
CONFIG_ARM_ERRATA_460075=y
@@ -58,7 +55,6 @@ CONFIG_MD=y
CONFIG_BLK_DEV_DM=y
CONFIG_NETDEVICES=y
# CONFIG_NET_VENDOR_BROADCOM is not set
-# CONFIG_NET_VENDOR_CHELSIO is not set
# CONFIG_NET_VENDOR_CIRRUS is not set
# CONFIG_NET_VENDOR_FARADAY is not set
# CONFIG_NET_VENDOR_INTEL is not set
@@ -89,16 +85,14 @@ CONFIG_I2C_SH_MOBILE=y
# CONFIG_HWMON is not set
CONFIG_REGULATOR=y
CONFIG_MEDIA_SUPPORT=y
-CONFIG_VIDEO_DEV=y
CONFIG_MEDIA_CAMERA_SUPPORT=y
CONFIG_V4L_PLATFORM_DRIVERS=y
CONFIG_SOC_CAMERA=y
-CONFIG_SOC_CAMERA_MT9T112=y
CONFIG_VIDEO_SH_MOBILE_CEU=y
+CONFIG_SOC_CAMERA_MT9T112=y
CONFIG_FB=y
CONFIG_FB_SH_MOBILE_LCDC=y
CONFIG_FB_SH_MOBILE_HDMI=y
-CONFIG_LCD_CLASS_DEVICE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_LOGO=y
@@ -109,12 +103,11 @@ CONFIG_LOGO=y
# CONFIG_SND_DRIVERS is not set
# CONFIG_SND_ARM is not set
CONFIG_SND_SOC_SH4_FSI=y
-# CONFIG_HID_SUPPORT is not set
CONFIG_USB=y
CONFIG_USB_RENESAS_USBHS=y
CONFIG_USB_GADGET=y
CONFIG_USB_RENESAS_USBHS_UDC=y
-CONFIG_USB_ETH=m
+CONFIG_USB_ETH=y
CONFIG_MMC=y
CONFIG_MMC_SDHI=y
CONFIG_MMC_SH_MMCIF=y
--
1.7.10.4
^ permalink raw reply related [flat|nested] 38+ messages in thread
* [RFC/PATCH 2/7] ARM: shmobile: make defconfig canonical
@ 2013-04-04 3:29 ` Simon Horman
0 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-04 3:29 UTC (permalink / raw)
To: linux-arm-kernel
Use make savedefconfig to update the defconfig to the current
canonical form.
This is to aid the process of adding support for other boards.
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
arch/arm/configs/shmobile_defconfig | 11 ++---------
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git a/arch/arm/configs/shmobile_defconfig b/arch/arm/configs/shmobile_defconfig
index 90f5600..fd1c074 100644
--- a/arch/arm/configs/shmobile_defconfig
+++ b/arch/arm/configs/shmobile_defconfig
@@ -1,4 +1,3 @@
-CONFIG_EXPERIMENTAL=y
CONFIG_SYSVIPC=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
@@ -13,8 +12,6 @@ CONFIG_ARCH_SHMOBILE=y
CONFIG_ARCH_R8A7740=y
CONFIG_MACH_ARMADILLO800EVA=y
# CONFIG_SH_TIMER_TMU is not set
-CONFIG_ARM_THUMB=y
-CONFIG_CACHE_L2X0=y
CONFIG_ARM_ERRATA_430973=y
CONFIG_ARM_ERRATA_458693=y
CONFIG_ARM_ERRATA_460075=y
@@ -58,7 +55,6 @@ CONFIG_MD=y
CONFIG_BLK_DEV_DM=y
CONFIG_NETDEVICES=y
# CONFIG_NET_VENDOR_BROADCOM is not set
-# CONFIG_NET_VENDOR_CHELSIO is not set
# CONFIG_NET_VENDOR_CIRRUS is not set
# CONFIG_NET_VENDOR_FARADAY is not set
# CONFIG_NET_VENDOR_INTEL is not set
@@ -89,16 +85,14 @@ CONFIG_I2C_SH_MOBILE=y
# CONFIG_HWMON is not set
CONFIG_REGULATOR=y
CONFIG_MEDIA_SUPPORT=y
-CONFIG_VIDEO_DEV=y
CONFIG_MEDIA_CAMERA_SUPPORT=y
CONFIG_V4L_PLATFORM_DRIVERS=y
CONFIG_SOC_CAMERA=y
-CONFIG_SOC_CAMERA_MT9T112=y
CONFIG_VIDEO_SH_MOBILE_CEU=y
+CONFIG_SOC_CAMERA_MT9T112=y
CONFIG_FB=y
CONFIG_FB_SH_MOBILE_LCDC=y
CONFIG_FB_SH_MOBILE_HDMI=y
-CONFIG_LCD_CLASS_DEVICE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_LOGO=y
@@ -109,12 +103,11 @@ CONFIG_LOGO=y
# CONFIG_SND_DRIVERS is not set
# CONFIG_SND_ARM is not set
CONFIG_SND_SOC_SH4_FSI=y
-# CONFIG_HID_SUPPORT is not set
CONFIG_USB=y
CONFIG_USB_RENESAS_USBHS=y
CONFIG_USB_GADGET=y
CONFIG_USB_RENESAS_USBHS_UDC=y
-CONFIG_USB_ETH=m
+CONFIG_USB_ETH=y
CONFIG_MMC=y
CONFIG_MMC_SDHI=y
CONFIG_MMC_SH_MMCIF=y
--
1.7.10.4
^ permalink raw reply related [flat|nested] 38+ messages in thread
* [RFC/PATCH 3/7] ARM: shmobile: Add kzm9d to consolidated defconfig
2013-04-04 3:29 ` Simon Horman
@ 2013-04-04 3:29 ` Simon Horman
-1 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-04 3:29 UTC (permalink / raw)
To: linux-arm-kernel
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
arch/arm/configs/shmobile_defconfig | 16 ++++++++++++++--
1 file changed, 14 insertions(+), 2 deletions(-)
diff --git a/arch/arm/configs/shmobile_defconfig b/arch/arm/configs/shmobile_defconfig
index fd1c074..8228e09 100644
--- a/arch/arm/configs/shmobile_defconfig
+++ b/arch/arm/configs/shmobile_defconfig
@@ -1,8 +1,11 @@
CONFIG_SYSVIPC=y
+CONFIG_NO_HZ=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT\x16
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
+CONFIG_SYSCTL_SYSCALL=y
+CONFIG_EMBEDDED=y
CONFIG_PERF_EVENTS=y
CONFIG_SLAB=y
# CONFIG_BLK_DEV_BSG is not set
@@ -10,8 +13,11 @@ CONFIG_SLAB=y
# CONFIG_IOSCHED_CFQ is not set
CONFIG_ARCH_SHMOBILE=y
CONFIG_ARCH_R8A7740=y
+CONFIG_ARCH_EMEV2=y
CONFIG_MACH_ARMADILLO800EVA=y
+CONFIG_MACH_KZM9D=y
# CONFIG_SH_TIMER_TMU is not set
+# CONFIG_SWP_EMULATE is not set
CONFIG_ARM_ERRATA_430973=y
CONFIG_ARM_ERRATA_458693=y
CONFIG_ARM_ERRATA_460075=y
@@ -24,6 +30,9 @@ CONFIG_PL310_ERRATA_753970=y
CONFIG_ARM_ERRATA_754322=y
CONFIG_PL310_ERRATA_769419=y
CONFIG_ARM_ERRATA_775420=y
+CONFIG_SMP=y
+CONFIG_NR_CPUS=2
+# CONFIG_LOCAL_TIMERS is not set
CONFIG_AEABI=y
# CONFIG_OABI_COMPAT is not set
CONFIG_FORCE_MAX_ZONEORDER\x13
@@ -63,18 +72,20 @@ CONFIG_NETDEVICES=y
# CONFIG_NET_VENDOR_NATSEMI is not set
CONFIG_SH_ETH=y
# CONFIG_NET_VENDOR_SEEQ is not set
-# CONFIG_NET_VENDOR_SMSC is not set
+CONFIG_SMSC911X=y
# CONFIG_NET_VENDOR_STMICRO is not set
# CONFIG_WLAN is not set
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_KEYBOARD_ATKBD is not set
-CONFIG_KEYBOARD_GPIO=y
# CONFIG_INPUT_MOUSE is not set
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_ST1232=y
# CONFIG_SERIO is not set
# CONFIG_LEGACY_PTYS is not set
+CONFIG_SERIAL_8250=y
+CONFIG_SERIAL_8250_CONSOLE=y
+CONFIG_SERIAL_8250_EM=y
CONFIG_SERIAL_SH_SCI=y
CONFIG_SERIAL_SH_SCI_NR_UARTS=8
CONFIG_SERIAL_SH_SCI_CONSOLE=y
@@ -82,6 +93,7 @@ CONFIG_SERIAL_SH_SCI_CONSOLE=y
CONFIG_I2C=y
CONFIG_I2C_GPIO=y
CONFIG_I2C_SH_MOBILE=y
+CONFIG_GPIO_EM=y
# CONFIG_HWMON is not set
CONFIG_REGULATOR=y
CONFIG_MEDIA_SUPPORT=y
--
1.7.10.4
^ permalink raw reply related [flat|nested] 38+ messages in thread
* [RFC/PATCH 3/7] ARM: shmobile: Add kzm9d to consolidated defconfig
@ 2013-04-04 3:29 ` Simon Horman
0 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-04 3:29 UTC (permalink / raw)
To: linux-arm-kernel
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
arch/arm/configs/shmobile_defconfig | 16 ++++++++++++++--
1 file changed, 14 insertions(+), 2 deletions(-)
diff --git a/arch/arm/configs/shmobile_defconfig b/arch/arm/configs/shmobile_defconfig
index fd1c074..8228e09 100644
--- a/arch/arm/configs/shmobile_defconfig
+++ b/arch/arm/configs/shmobile_defconfig
@@ -1,8 +1,11 @@
CONFIG_SYSVIPC=y
+CONFIG_NO_HZ=y
CONFIG_IKCONFIG=y
CONFIG_IKCONFIG_PROC=y
CONFIG_LOG_BUF_SHIFT=16
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
+CONFIG_SYSCTL_SYSCALL=y
+CONFIG_EMBEDDED=y
CONFIG_PERF_EVENTS=y
CONFIG_SLAB=y
# CONFIG_BLK_DEV_BSG is not set
@@ -10,8 +13,11 @@ CONFIG_SLAB=y
# CONFIG_IOSCHED_CFQ is not set
CONFIG_ARCH_SHMOBILE=y
CONFIG_ARCH_R8A7740=y
+CONFIG_ARCH_EMEV2=y
CONFIG_MACH_ARMADILLO800EVA=y
+CONFIG_MACH_KZM9D=y
# CONFIG_SH_TIMER_TMU is not set
+# CONFIG_SWP_EMULATE is not set
CONFIG_ARM_ERRATA_430973=y
CONFIG_ARM_ERRATA_458693=y
CONFIG_ARM_ERRATA_460075=y
@@ -24,6 +30,9 @@ CONFIG_PL310_ERRATA_753970=y
CONFIG_ARM_ERRATA_754322=y
CONFIG_PL310_ERRATA_769419=y
CONFIG_ARM_ERRATA_775420=y
+CONFIG_SMP=y
+CONFIG_NR_CPUS=2
+# CONFIG_LOCAL_TIMERS is not set
CONFIG_AEABI=y
# CONFIG_OABI_COMPAT is not set
CONFIG_FORCE_MAX_ZONEORDER=13
@@ -63,18 +72,20 @@ CONFIG_NETDEVICES=y
# CONFIG_NET_VENDOR_NATSEMI is not set
CONFIG_SH_ETH=y
# CONFIG_NET_VENDOR_SEEQ is not set
-# CONFIG_NET_VENDOR_SMSC is not set
+CONFIG_SMSC911X=y
# CONFIG_NET_VENDOR_STMICRO is not set
# CONFIG_WLAN is not set
# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
CONFIG_INPUT_EVDEV=y
# CONFIG_KEYBOARD_ATKBD is not set
-CONFIG_KEYBOARD_GPIO=y
# CONFIG_INPUT_MOUSE is not set
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_ST1232=y
# CONFIG_SERIO is not set
# CONFIG_LEGACY_PTYS is not set
+CONFIG_SERIAL_8250=y
+CONFIG_SERIAL_8250_CONSOLE=y
+CONFIG_SERIAL_8250_EM=y
CONFIG_SERIAL_SH_SCI=y
CONFIG_SERIAL_SH_SCI_NR_UARTS=8
CONFIG_SERIAL_SH_SCI_CONSOLE=y
@@ -82,6 +93,7 @@ CONFIG_SERIAL_SH_SCI_CONSOLE=y
CONFIG_I2C=y
CONFIG_I2C_GPIO=y
CONFIG_I2C_SH_MOBILE=y
+CONFIG_GPIO_EM=y
# CONFIG_HWMON is not set
CONFIG_REGULATOR=y
CONFIG_MEDIA_SUPPORT=y
--
1.7.10.4
^ permalink raw reply related [flat|nested] 38+ messages in thread
* [RFC/PATCH 4/7] ARM: shmobile: Add mackerel to consolidated defconfig
2013-04-04 3:29 ` Simon Horman
@ 2013-04-04 3:29 ` Simon Horman
-1 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-04 3:29 UTC (permalink / raw)
To: linux-arm-kernel
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
arch/arm/configs/shmobile_defconfig | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/arch/arm/configs/shmobile_defconfig b/arch/arm/configs/shmobile_defconfig
index 8228e09..9b6219a 100644
--- a/arch/arm/configs/shmobile_defconfig
+++ b/arch/arm/configs/shmobile_defconfig
@@ -12,8 +12,10 @@ CONFIG_SLAB=y
# CONFIG_IOSCHED_DEADLINE is not set
# CONFIG_IOSCHED_CFQ is not set
CONFIG_ARCH_SHMOBILE=y
+CONFIG_ARCH_SH7372=y
CONFIG_ARCH_R8A7740=y
CONFIG_ARCH_EMEV2=y
+CONFIG_MACH_MACKEREL=y
CONFIG_MACH_ARMADILLO800EVA=y
CONFIG_MACH_KZM9D=y
# CONFIG_SH_TIMER_TMU is not set
@@ -58,6 +60,14 @@ CONFIG_IP_PNP_DHCP=y
# CONFIG_IPV6 is not set
# CONFIG_WIRELESS is not set
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
+CONFIG_MTD=y
+CONFIG_MTD_CHAR=y
+CONFIG_MTD_BLOCK=y
+CONFIG_MTD_CFI=y
+CONFIG_MTD_CFI_ADV_OPTIONS=y
+CONFIG_MTD_CFI_INTELEXT=y
+CONFIG_MTD_PHYSMAP=y
+CONFIG_MTD_BLOCK2MTD=y
CONFIG_SCSI=y
CONFIG_BLK_DEV_SD=y
CONFIG_MD=y
@@ -116,7 +126,9 @@ CONFIG_LOGO=y
# CONFIG_SND_ARM is not set
CONFIG_SND_SOC_SH4_FSI=y
CONFIG_USB=y
+CONFIG_USB_RENESAS_USBHS_HCD=y
CONFIG_USB_RENESAS_USBHS=y
+CONFIG_USB_STORAGE=y
CONFIG_USB_GADGET=y
CONFIG_USB_RENESAS_USBHS_UDC=y
CONFIG_USB_ETH=y
--
1.7.10.4
^ permalink raw reply related [flat|nested] 38+ messages in thread
* [RFC/PATCH 4/7] ARM: shmobile: Add mackerel to consolidated defconfig
@ 2013-04-04 3:29 ` Simon Horman
0 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-04 3:29 UTC (permalink / raw)
To: linux-arm-kernel
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
arch/arm/configs/shmobile_defconfig | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/arch/arm/configs/shmobile_defconfig b/arch/arm/configs/shmobile_defconfig
index 8228e09..9b6219a 100644
--- a/arch/arm/configs/shmobile_defconfig
+++ b/arch/arm/configs/shmobile_defconfig
@@ -12,8 +12,10 @@ CONFIG_SLAB=y
# CONFIG_IOSCHED_DEADLINE is not set
# CONFIG_IOSCHED_CFQ is not set
CONFIG_ARCH_SHMOBILE=y
+CONFIG_ARCH_SH7372=y
CONFIG_ARCH_R8A7740=y
CONFIG_ARCH_EMEV2=y
+CONFIG_MACH_MACKEREL=y
CONFIG_MACH_ARMADILLO800EVA=y
CONFIG_MACH_KZM9D=y
# CONFIG_SH_TIMER_TMU is not set
@@ -58,6 +60,14 @@ CONFIG_IP_PNP_DHCP=y
# CONFIG_IPV6 is not set
# CONFIG_WIRELESS is not set
CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
+CONFIG_MTD=y
+CONFIG_MTD_CHAR=y
+CONFIG_MTD_BLOCK=y
+CONFIG_MTD_CFI=y
+CONFIG_MTD_CFI_ADV_OPTIONS=y
+CONFIG_MTD_CFI_INTELEXT=y
+CONFIG_MTD_PHYSMAP=y
+CONFIG_MTD_BLOCK2MTD=y
CONFIG_SCSI=y
CONFIG_BLK_DEV_SD=y
CONFIG_MD=y
@@ -116,7 +126,9 @@ CONFIG_LOGO=y
# CONFIG_SND_ARM is not set
CONFIG_SND_SOC_SH4_FSI=y
CONFIG_USB=y
+CONFIG_USB_RENESAS_USBHS_HCD=y
CONFIG_USB_RENESAS_USBHS=y
+CONFIG_USB_STORAGE=y
CONFIG_USB_GADGET=y
CONFIG_USB_RENESAS_USBHS_UDC=y
CONFIG_USB_ETH=y
--
1.7.10.4
^ permalink raw reply related [flat|nested] 38+ messages in thread
* [RFC/PATCH 5/7] ARM: shmobile: defconfig: Remove armadillo800eva defconfig
2013-04-04 3:29 ` Simon Horman
@ 2013-04-04 3:29 ` Simon Horman
-1 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-04 3:29 UTC (permalink / raw)
To: linux-arm-kernel
Remove armadillo800eva defconfig as the shmobile defconfig may now be used
instead.
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
arch/arm/configs/armadillo800eva_defconfig | 153 ----------------------------
1 file changed, 153 deletions(-)
delete mode 100644 arch/arm/configs/armadillo800eva_defconfig
diff --git a/arch/arm/configs/armadillo800eva_defconfig b/arch/arm/configs/armadillo800eva_defconfig
deleted file mode 100644
index 0f2d80d..0000000
--- a/arch/arm/configs/armadillo800eva_defconfig
+++ /dev/null
@@ -1,153 +0,0 @@
-CONFIG_EXPERIMENTAL=y
-CONFIG_SYSVIPC=y
-CONFIG_IKCONFIG=y
-CONFIG_IKCONFIG_PROC=y
-CONFIG_LOG_BUF_SHIFT\x16
-# CONFIG_UTS_NS is not set
-# CONFIG_IPC_NS is not set
-# CONFIG_PID_NS is not set
-CONFIG_CC_OPTIMIZE_FOR_SIZE=y
-CONFIG_PERF_EVENTS=y
-CONFIG_SLAB=y
-CONFIG_MODULES=y
-CONFIG_MODULE_UNLOAD=y
-CONFIG_MODULE_FORCE_UNLOAD=y
-# CONFIG_BLK_DEV_BSG is not set
-# CONFIG_IOSCHED_DEADLINE is not set
-# CONFIG_IOSCHED_CFQ is not set
-CONFIG_ARCH_SHMOBILE=y
-CONFIG_ARCH_R8A7740=y
-CONFIG_MACH_ARMADILLO800EVA=y
-# CONFIG_SH_TIMER_TMU is not set
-CONFIG_ARM_THUMB=y
-CONFIG_CACHE_L2X0=y
-CONFIG_ARM_ERRATA_430973=y
-CONFIG_ARM_ERRATA_458693=y
-CONFIG_ARM_ERRATA_460075=y
-CONFIG_PL310_ERRATA_588369=y
-CONFIG_ARM_ERRATA_720789=y
-CONFIG_PL310_ERRATA_727915=y
-CONFIG_ARM_ERRATA_743622=y
-CONFIG_ARM_ERRATA_751472=y
-CONFIG_PL310_ERRATA_753970=y
-CONFIG_ARM_ERRATA_754322=y
-CONFIG_PL310_ERRATA_769419=y
-CONFIG_ARM_ERRATA_775420=y
-CONFIG_AEABI=y
-# CONFIG_OABI_COMPAT is not set
-CONFIG_FORCE_MAX_ZONEORDER\x13
-CONFIG_ZBOOT_ROM_TEXT=0x0
-CONFIG_ZBOOT_ROM_BSS=0x0
-CONFIG_ARM_APPENDED_DTB=y
-CONFIG_KEXEC=y
-CONFIG_VFP=y
-CONFIG_NEON=y
-# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
-CONFIG_PM_RUNTIME=y
-CONFIG_NET=y
-CONFIG_PACKET=y
-CONFIG_UNIX=y
-CONFIG_INET=y
-CONFIG_IP_PNP=y
-CONFIG_IP_PNP_DHCP=y
-# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
-# CONFIG_INET_XFRM_MODE_TUNNEL is not set
-# CONFIG_INET_XFRM_MODE_BEET is not set
-# CONFIG_INET_LRO is not set
-# CONFIG_INET_DIAG is not set
-# CONFIG_IPV6 is not set
-# CONFIG_WIRELESS is not set
-CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
-CONFIG_SCSI=y
-CONFIG_BLK_DEV_SD=y
-CONFIG_MD=y
-CONFIG_BLK_DEV_DM=y
-CONFIG_NETDEVICES=y
-# CONFIG_NET_VENDOR_BROADCOM is not set
-# CONFIG_NET_VENDOR_CHELSIO is not set
-# CONFIG_NET_VENDOR_CIRRUS is not set
-# CONFIG_NET_VENDOR_FARADAY is not set
-# CONFIG_NET_VENDOR_INTEL is not set
-# CONFIG_NET_VENDOR_MARVELL is not set
-# CONFIG_NET_VENDOR_MICREL is not set
-# CONFIG_NET_VENDOR_NATSEMI is not set
-CONFIG_SH_ETH=y
-# CONFIG_NET_VENDOR_SEEQ is not set
-# CONFIG_NET_VENDOR_SMSC is not set
-# CONFIG_NET_VENDOR_STMICRO is not set
-# CONFIG_WLAN is not set
-# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
-CONFIG_INPUT_EVDEV=y
-# CONFIG_KEYBOARD_ATKBD is not set
-CONFIG_KEYBOARD_GPIO=y
-# CONFIG_INPUT_MOUSE is not set
-CONFIG_INPUT_TOUCHSCREEN=y
-CONFIG_TOUCHSCREEN_ST1232=y
-# CONFIG_SERIO is not set
-# CONFIG_LEGACY_PTYS is not set
-CONFIG_SERIAL_SH_SCI=y
-CONFIG_SERIAL_SH_SCI_NR_UARTS=8
-CONFIG_SERIAL_SH_SCI_CONSOLE=y
-# CONFIG_HW_RANDOM is not set
-CONFIG_I2C=y
-CONFIG_I2C_GPIO=y
-CONFIG_I2C_SH_MOBILE=y
-# CONFIG_HWMON is not set
-CONFIG_REGULATOR=y
-CONFIG_MEDIA_SUPPORT=y
-CONFIG_VIDEO_DEV=y
-CONFIG_MEDIA_CAMERA_SUPPORT=y
-CONFIG_V4L_PLATFORM_DRIVERS=y
-CONFIG_SOC_CAMERA=y
-CONFIG_SOC_CAMERA_MT9T112=y
-CONFIG_VIDEO_SH_MOBILE_CEU=y
-CONFIG_FB=y
-CONFIG_FB_SH_MOBILE_LCDC=y
-CONFIG_FB_SH_MOBILE_HDMI=y
-CONFIG_LCD_CLASS_DEVICE=y
-CONFIG_FRAMEBUFFER_CONSOLE=y
-CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
-CONFIG_LOGO=y
-# CONFIG_LOGO_LINUX_MONO is not set
-# CONFIG_LOGO_LINUX_VGA16 is not set
-# CONFIG_SND_SUPPORT_OLD_API is not set
-# CONFIG_SND_VERBOSE_PROCFS is not set
-# CONFIG_SND_DRIVERS is not set
-# CONFIG_SND_ARM is not set
-CONFIG_SND_SOC_SH4_FSI=y
-# CONFIG_HID_SUPPORT is not set
-CONFIG_USB=y
-CONFIG_USB_RENESAS_USBHS=y
-CONFIG_USB_GADGET=y
-CONFIG_USB_RENESAS_USBHS_UDC=y
-CONFIG_USB_ETH=m
-CONFIG_MMC=y
-CONFIG_MMC_SDHI=y
-CONFIG_MMC_SH_MMCIF=y
-CONFIG_RTC_CLASS=y
-CONFIG_RTC_DRV_S35390A=y
-CONFIG_DMADEVICES=y
-CONFIG_SH_DMAE=y
-CONFIG_UIO=y
-CONFIG_UIO_PDRV_GENIRQ=y
-# CONFIG_DNOTIFY is not set
-CONFIG_MSDOS_FS=y
-CONFIG_VFAT_FS=y
-CONFIG_TMPFS=y
-# CONFIG_MISC_FILESYSTEMS is not set
-CONFIG_NFS_FS=y
-CONFIG_NFS_V3_ACL=y
-CONFIG_NFS_V4=y
-CONFIG_NFS_V4_1=y
-CONFIG_ROOT_NFS=y
-CONFIG_NLS_CODEPAGE_437=y
-CONFIG_NLS_ISO8859_1=y
-# CONFIG_ENABLE_WARN_DEPRECATED is not set
-# CONFIG_ENABLE_MUST_CHECK is not set
-# CONFIG_ARM_UNWIND is not set
-CONFIG_CRYPTO=y
-CONFIG_CRYPTO_CBC=y
-CONFIG_CRYPTO_MD5=y
-CONFIG_CRYPTO_DES=y
-CONFIG_CRYPTO_ANSI_CPRNG=y
-CONFIG_XZ_DEC=y
--
1.7.10.4
^ permalink raw reply related [flat|nested] 38+ messages in thread
* [RFC/PATCH 5/7] ARM: shmobile: defconfig: Remove armadillo800eva defconfig
@ 2013-04-04 3:29 ` Simon Horman
0 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-04 3:29 UTC (permalink / raw)
To: linux-arm-kernel
Remove armadillo800eva defconfig as the shmobile defconfig may now be used
instead.
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
arch/arm/configs/armadillo800eva_defconfig | 153 ----------------------------
1 file changed, 153 deletions(-)
delete mode 100644 arch/arm/configs/armadillo800eva_defconfig
diff --git a/arch/arm/configs/armadillo800eva_defconfig b/arch/arm/configs/armadillo800eva_defconfig
deleted file mode 100644
index 0f2d80d..0000000
--- a/arch/arm/configs/armadillo800eva_defconfig
+++ /dev/null
@@ -1,153 +0,0 @@
-CONFIG_EXPERIMENTAL=y
-CONFIG_SYSVIPC=y
-CONFIG_IKCONFIG=y
-CONFIG_IKCONFIG_PROC=y
-CONFIG_LOG_BUF_SHIFT=16
-# CONFIG_UTS_NS is not set
-# CONFIG_IPC_NS is not set
-# CONFIG_PID_NS is not set
-CONFIG_CC_OPTIMIZE_FOR_SIZE=y
-CONFIG_PERF_EVENTS=y
-CONFIG_SLAB=y
-CONFIG_MODULES=y
-CONFIG_MODULE_UNLOAD=y
-CONFIG_MODULE_FORCE_UNLOAD=y
-# CONFIG_BLK_DEV_BSG is not set
-# CONFIG_IOSCHED_DEADLINE is not set
-# CONFIG_IOSCHED_CFQ is not set
-CONFIG_ARCH_SHMOBILE=y
-CONFIG_ARCH_R8A7740=y
-CONFIG_MACH_ARMADILLO800EVA=y
-# CONFIG_SH_TIMER_TMU is not set
-CONFIG_ARM_THUMB=y
-CONFIG_CACHE_L2X0=y
-CONFIG_ARM_ERRATA_430973=y
-CONFIG_ARM_ERRATA_458693=y
-CONFIG_ARM_ERRATA_460075=y
-CONFIG_PL310_ERRATA_588369=y
-CONFIG_ARM_ERRATA_720789=y
-CONFIG_PL310_ERRATA_727915=y
-CONFIG_ARM_ERRATA_743622=y
-CONFIG_ARM_ERRATA_751472=y
-CONFIG_PL310_ERRATA_753970=y
-CONFIG_ARM_ERRATA_754322=y
-CONFIG_PL310_ERRATA_769419=y
-CONFIG_ARM_ERRATA_775420=y
-CONFIG_AEABI=y
-# CONFIG_OABI_COMPAT is not set
-CONFIG_FORCE_MAX_ZONEORDER=13
-CONFIG_ZBOOT_ROM_TEXT=0x0
-CONFIG_ZBOOT_ROM_BSS=0x0
-CONFIG_ARM_APPENDED_DTB=y
-CONFIG_KEXEC=y
-CONFIG_VFP=y
-CONFIG_NEON=y
-# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
-CONFIG_PM_RUNTIME=y
-CONFIG_NET=y
-CONFIG_PACKET=y
-CONFIG_UNIX=y
-CONFIG_INET=y
-CONFIG_IP_PNP=y
-CONFIG_IP_PNP_DHCP=y
-# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
-# CONFIG_INET_XFRM_MODE_TUNNEL is not set
-# CONFIG_INET_XFRM_MODE_BEET is not set
-# CONFIG_INET_LRO is not set
-# CONFIG_INET_DIAG is not set
-# CONFIG_IPV6 is not set
-# CONFIG_WIRELESS is not set
-CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
-CONFIG_SCSI=y
-CONFIG_BLK_DEV_SD=y
-CONFIG_MD=y
-CONFIG_BLK_DEV_DM=y
-CONFIG_NETDEVICES=y
-# CONFIG_NET_VENDOR_BROADCOM is not set
-# CONFIG_NET_VENDOR_CHELSIO is not set
-# CONFIG_NET_VENDOR_CIRRUS is not set
-# CONFIG_NET_VENDOR_FARADAY is not set
-# CONFIG_NET_VENDOR_INTEL is not set
-# CONFIG_NET_VENDOR_MARVELL is not set
-# CONFIG_NET_VENDOR_MICREL is not set
-# CONFIG_NET_VENDOR_NATSEMI is not set
-CONFIG_SH_ETH=y
-# CONFIG_NET_VENDOR_SEEQ is not set
-# CONFIG_NET_VENDOR_SMSC is not set
-# CONFIG_NET_VENDOR_STMICRO is not set
-# CONFIG_WLAN is not set
-# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
-CONFIG_INPUT_EVDEV=y
-# CONFIG_KEYBOARD_ATKBD is not set
-CONFIG_KEYBOARD_GPIO=y
-# CONFIG_INPUT_MOUSE is not set
-CONFIG_INPUT_TOUCHSCREEN=y
-CONFIG_TOUCHSCREEN_ST1232=y
-# CONFIG_SERIO is not set
-# CONFIG_LEGACY_PTYS is not set
-CONFIG_SERIAL_SH_SCI=y
-CONFIG_SERIAL_SH_SCI_NR_UARTS=8
-CONFIG_SERIAL_SH_SCI_CONSOLE=y
-# CONFIG_HW_RANDOM is not set
-CONFIG_I2C=y
-CONFIG_I2C_GPIO=y
-CONFIG_I2C_SH_MOBILE=y
-# CONFIG_HWMON is not set
-CONFIG_REGULATOR=y
-CONFIG_MEDIA_SUPPORT=y
-CONFIG_VIDEO_DEV=y
-CONFIG_MEDIA_CAMERA_SUPPORT=y
-CONFIG_V4L_PLATFORM_DRIVERS=y
-CONFIG_SOC_CAMERA=y
-CONFIG_SOC_CAMERA_MT9T112=y
-CONFIG_VIDEO_SH_MOBILE_CEU=y
-CONFIG_FB=y
-CONFIG_FB_SH_MOBILE_LCDC=y
-CONFIG_FB_SH_MOBILE_HDMI=y
-CONFIG_LCD_CLASS_DEVICE=y
-CONFIG_FRAMEBUFFER_CONSOLE=y
-CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
-CONFIG_LOGO=y
-# CONFIG_LOGO_LINUX_MONO is not set
-# CONFIG_LOGO_LINUX_VGA16 is not set
-# CONFIG_SND_SUPPORT_OLD_API is not set
-# CONFIG_SND_VERBOSE_PROCFS is not set
-# CONFIG_SND_DRIVERS is not set
-# CONFIG_SND_ARM is not set
-CONFIG_SND_SOC_SH4_FSI=y
-# CONFIG_HID_SUPPORT is not set
-CONFIG_USB=y
-CONFIG_USB_RENESAS_USBHS=y
-CONFIG_USB_GADGET=y
-CONFIG_USB_RENESAS_USBHS_UDC=y
-CONFIG_USB_ETH=m
-CONFIG_MMC=y
-CONFIG_MMC_SDHI=y
-CONFIG_MMC_SH_MMCIF=y
-CONFIG_RTC_CLASS=y
-CONFIG_RTC_DRV_S35390A=y
-CONFIG_DMADEVICES=y
-CONFIG_SH_DMAE=y
-CONFIG_UIO=y
-CONFIG_UIO_PDRV_GENIRQ=y
-# CONFIG_DNOTIFY is not set
-CONFIG_MSDOS_FS=y
-CONFIG_VFAT_FS=y
-CONFIG_TMPFS=y
-# CONFIG_MISC_FILESYSTEMS is not set
-CONFIG_NFS_FS=y
-CONFIG_NFS_V3_ACL=y
-CONFIG_NFS_V4=y
-CONFIG_NFS_V4_1=y
-CONFIG_ROOT_NFS=y
-CONFIG_NLS_CODEPAGE_437=y
-CONFIG_NLS_ISO8859_1=y
-# CONFIG_ENABLE_WARN_DEPRECATED is not set
-# CONFIG_ENABLE_MUST_CHECK is not set
-# CONFIG_ARM_UNWIND is not set
-CONFIG_CRYPTO=y
-CONFIG_CRYPTO_CBC=y
-CONFIG_CRYPTO_MD5=y
-CONFIG_CRYPTO_DES=y
-CONFIG_CRYPTO_ANSI_CPRNG=y
-CONFIG_XZ_DEC=y
--
1.7.10.4
^ permalink raw reply related [flat|nested] 38+ messages in thread
* [RFC/PATCH 6/7] ARM: shmobile: defconfig: Remove kzm9d defconfig
2013-04-04 3:29 ` Simon Horman
@ 2013-04-04 3:29 ` Simon Horman
-1 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-04 3:29 UTC (permalink / raw)
To: linux-arm-kernel
Remove kzm9d defconfig as the shmobile defconfig may now be used instead.
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
arch/arm/configs/kzm9d_defconfig | 88 --------------------------------------
1 file changed, 88 deletions(-)
delete mode 100644 arch/arm/configs/kzm9d_defconfig
diff --git a/arch/arm/configs/kzm9d_defconfig b/arch/arm/configs/kzm9d_defconfig
deleted file mode 100644
index 6c37f4a..0000000
--- a/arch/arm/configs/kzm9d_defconfig
+++ /dev/null
@@ -1,88 +0,0 @@
-# CONFIG_ARM_PATCH_PHYS_VIRT is not set
-CONFIG_EXPERIMENTAL=y
-CONFIG_SYSVIPC=y
-CONFIG_NO_HZ=y
-CONFIG_IKCONFIG=y
-CONFIG_IKCONFIG_PROC=y
-CONFIG_LOG_BUF_SHIFT\x16
-CONFIG_CC_OPTIMIZE_FOR_SIZE=y
-CONFIG_SYSCTL_SYSCALL=y
-CONFIG_EMBEDDED=y
-CONFIG_PERF_EVENTS=y
-CONFIG_SLAB=y
-# CONFIG_BLK_DEV_BSG is not set
-# CONFIG_IOSCHED_DEADLINE is not set
-# CONFIG_IOSCHED_CFQ is not set
-CONFIG_ARCH_SHMOBILE=y
-CONFIG_ARCH_EMEV2=y
-CONFIG_MACH_KZM9D=y
-CONFIG_MEMORY_START=0x40000000
-CONFIG_MEMORY_SIZE=0x10000000
-# CONFIG_SH_TIMER_TMU is not set
-# CONFIG_SWP_EMULATE is not set
-# CONFIG_CACHE_L2X0 is not set
-CONFIG_SMP=y
-CONFIG_NR_CPUS=2
-CONFIG_HOTPLUG_CPU=y
-# CONFIG_LOCAL_TIMERS is not set
-CONFIG_AEABI=y
-# CONFIG_OABI_COMPAT is not set
-# CONFIG_CROSS_MEMORY_ATTACH is not set
-CONFIG_FORCE_MAX_ZONEORDER\x13
-CONFIG_ZBOOT_ROM_TEXT=0x0
-CONFIG_ZBOOT_ROM_BSS=0x0
-CONFIG_ARM_APPENDED_DTB=y
-CONFIG_VFP=y
-# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
-CONFIG_PM_RUNTIME=y
-CONFIG_NET=y
-CONFIG_PACKET=y
-CONFIG_UNIX=y
-CONFIG_INET=y
-CONFIG_IP_PNP=y
-CONFIG_IP_PNP_DHCP=y
-# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
-# CONFIG_INET_XFRM_MODE_TUNNEL is not set
-# CONFIG_INET_XFRM_MODE_BEET is not set
-# CONFIG_INET_LRO is not set
-# CONFIG_INET_DIAG is not set
-# CONFIG_IPV6 is not set
-# CONFIG_WIRELESS is not set
-CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
-# CONFIG_BLK_DEV is not set
-CONFIG_NETDEVICES=y
-# CONFIG_NET_VENDOR_BROADCOM is not set
-# CONFIG_NET_VENDOR_CHELSIO is not set
-# CONFIG_NET_VENDOR_CIRRUS is not set
-# CONFIG_NET_VENDOR_FARADAY is not set
-# CONFIG_NET_VENDOR_INTEL is not set
-# CONFIG_NET_VENDOR_MARVELL is not set
-# CONFIG_NET_VENDOR_MICREL is not set
-# CONFIG_NET_VENDOR_NATSEMI is not set
-# CONFIG_NET_VENDOR_SEEQ is not set
-CONFIG_SMSC911X=y
-# CONFIG_NET_VENDOR_STMICRO is not set
-# CONFIG_NET_VENDOR_WIZNET is not set
-# CONFIG_WLAN is not set
-# CONFIG_INPUT_MOUSEDEV is not set
-# CONFIG_INPUT_KEYBOARD is not set
-# CONFIG_INPUT_MOUSE is not set
-# CONFIG_SERIO is not set
-# CONFIG_LEGACY_PTYS is not set
-# CONFIG_DEVKMEM is not set
-CONFIG_SERIAL_8250=y
-CONFIG_SERIAL_8250_CONSOLE=y
-CONFIG_SERIAL_8250_EM=y
-# CONFIG_HW_RANDOM is not set
-CONFIG_GPIOLIB=y
-CONFIG_GPIO_EM=y
-# CONFIG_HWMON is not set
-# CONFIG_HID_SUPPORT is not set
-# CONFIG_USB_SUPPORT is not set
-# CONFIG_IOMMU_SUPPORT is not set
-# CONFIG_DNOTIFY is not set
-CONFIG_TMPFS=y
-# CONFIG_MISC_FILESYSTEMS is not set
-CONFIG_NFS_FS=y
-CONFIG_ROOT_NFS=y
-# CONFIG_FTRACE is not set
--
1.7.10.4
^ permalink raw reply related [flat|nested] 38+ messages in thread
* [RFC/PATCH 6/7] ARM: shmobile: defconfig: Remove kzm9d defconfig
@ 2013-04-04 3:29 ` Simon Horman
0 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-04 3:29 UTC (permalink / raw)
To: linux-arm-kernel
Remove kzm9d defconfig as the shmobile defconfig may now be used instead.
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
arch/arm/configs/kzm9d_defconfig | 88 --------------------------------------
1 file changed, 88 deletions(-)
delete mode 100644 arch/arm/configs/kzm9d_defconfig
diff --git a/arch/arm/configs/kzm9d_defconfig b/arch/arm/configs/kzm9d_defconfig
deleted file mode 100644
index 6c37f4a..0000000
--- a/arch/arm/configs/kzm9d_defconfig
+++ /dev/null
@@ -1,88 +0,0 @@
-# CONFIG_ARM_PATCH_PHYS_VIRT is not set
-CONFIG_EXPERIMENTAL=y
-CONFIG_SYSVIPC=y
-CONFIG_NO_HZ=y
-CONFIG_IKCONFIG=y
-CONFIG_IKCONFIG_PROC=y
-CONFIG_LOG_BUF_SHIFT=16
-CONFIG_CC_OPTIMIZE_FOR_SIZE=y
-CONFIG_SYSCTL_SYSCALL=y
-CONFIG_EMBEDDED=y
-CONFIG_PERF_EVENTS=y
-CONFIG_SLAB=y
-# CONFIG_BLK_DEV_BSG is not set
-# CONFIG_IOSCHED_DEADLINE is not set
-# CONFIG_IOSCHED_CFQ is not set
-CONFIG_ARCH_SHMOBILE=y
-CONFIG_ARCH_EMEV2=y
-CONFIG_MACH_KZM9D=y
-CONFIG_MEMORY_START=0x40000000
-CONFIG_MEMORY_SIZE=0x10000000
-# CONFIG_SH_TIMER_TMU is not set
-# CONFIG_SWP_EMULATE is not set
-# CONFIG_CACHE_L2X0 is not set
-CONFIG_SMP=y
-CONFIG_NR_CPUS=2
-CONFIG_HOTPLUG_CPU=y
-# CONFIG_LOCAL_TIMERS is not set
-CONFIG_AEABI=y
-# CONFIG_OABI_COMPAT is not set
-# CONFIG_CROSS_MEMORY_ATTACH is not set
-CONFIG_FORCE_MAX_ZONEORDER=13
-CONFIG_ZBOOT_ROM_TEXT=0x0
-CONFIG_ZBOOT_ROM_BSS=0x0
-CONFIG_ARM_APPENDED_DTB=y
-CONFIG_VFP=y
-# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
-CONFIG_PM_RUNTIME=y
-CONFIG_NET=y
-CONFIG_PACKET=y
-CONFIG_UNIX=y
-CONFIG_INET=y
-CONFIG_IP_PNP=y
-CONFIG_IP_PNP_DHCP=y
-# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
-# CONFIG_INET_XFRM_MODE_TUNNEL is not set
-# CONFIG_INET_XFRM_MODE_BEET is not set
-# CONFIG_INET_LRO is not set
-# CONFIG_INET_DIAG is not set
-# CONFIG_IPV6 is not set
-# CONFIG_WIRELESS is not set
-CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
-# CONFIG_BLK_DEV is not set
-CONFIG_NETDEVICES=y
-# CONFIG_NET_VENDOR_BROADCOM is not set
-# CONFIG_NET_VENDOR_CHELSIO is not set
-# CONFIG_NET_VENDOR_CIRRUS is not set
-# CONFIG_NET_VENDOR_FARADAY is not set
-# CONFIG_NET_VENDOR_INTEL is not set
-# CONFIG_NET_VENDOR_MARVELL is not set
-# CONFIG_NET_VENDOR_MICREL is not set
-# CONFIG_NET_VENDOR_NATSEMI is not set
-# CONFIG_NET_VENDOR_SEEQ is not set
-CONFIG_SMSC911X=y
-# CONFIG_NET_VENDOR_STMICRO is not set
-# CONFIG_NET_VENDOR_WIZNET is not set
-# CONFIG_WLAN is not set
-# CONFIG_INPUT_MOUSEDEV is not set
-# CONFIG_INPUT_KEYBOARD is not set
-# CONFIG_INPUT_MOUSE is not set
-# CONFIG_SERIO is not set
-# CONFIG_LEGACY_PTYS is not set
-# CONFIG_DEVKMEM is not set
-CONFIG_SERIAL_8250=y
-CONFIG_SERIAL_8250_CONSOLE=y
-CONFIG_SERIAL_8250_EM=y
-# CONFIG_HW_RANDOM is not set
-CONFIG_GPIOLIB=y
-CONFIG_GPIO_EM=y
-# CONFIG_HWMON is not set
-# CONFIG_HID_SUPPORT is not set
-# CONFIG_USB_SUPPORT is not set
-# CONFIG_IOMMU_SUPPORT is not set
-# CONFIG_DNOTIFY is not set
-CONFIG_TMPFS=y
-# CONFIG_MISC_FILESYSTEMS is not set
-CONFIG_NFS_FS=y
-CONFIG_ROOT_NFS=y
-# CONFIG_FTRACE is not set
--
1.7.10.4
^ permalink raw reply related [flat|nested] 38+ messages in thread
* [RFC/PATCH 7/7] ARM: shmobile: defconfig: Remove mackerel defconfig
2013-04-04 3:29 ` Simon Horman
@ 2013-04-04 3:29 ` Simon Horman
-1 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-04 3:29 UTC (permalink / raw)
To: linux-arm-kernel
Remove mackerel defconfig as the shmobile defconfig may now be used instead.
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
arch/arm/configs/mackerel_defconfig | 156 -----------------------------------
1 file changed, 156 deletions(-)
delete mode 100644 arch/arm/configs/mackerel_defconfig
diff --git a/arch/arm/configs/mackerel_defconfig b/arch/arm/configs/mackerel_defconfig
deleted file mode 100644
index 9fb1189..0000000
--- a/arch/arm/configs/mackerel_defconfig
+++ /dev/null
@@ -1,156 +0,0 @@
-CONFIG_EXPERIMENTAL=y
-CONFIG_SYSVIPC=y
-CONFIG_IKCONFIG=y
-CONFIG_IKCONFIG_PROC=y
-CONFIG_LOG_BUF_SHIFT\x16
-# CONFIG_UTS_NS is not set
-# CONFIG_IPC_NS is not set
-# CONFIG_USER_NS is not set
-# CONFIG_PID_NS is not set
-# CONFIG_NET_NS is not set
-CONFIG_SLAB=y
-CONFIG_MODULES=y
-CONFIG_MODULE_UNLOAD=y
-# CONFIG_BLK_DEV_BSG is not set
-# CONFIG_IOSCHED_DEADLINE is not set
-# CONFIG_IOSCHED_CFQ is not set
-CONFIG_ARCH_SHMOBILE=y
-CONFIG_ARCH_SH7372=y
-CONFIG_MACH_MACKEREL=y
-CONFIG_MEMORY_SIZE=0x10000000
-CONFIG_AEABI=y
-# CONFIG_OABI_COMPAT is not set
-CONFIG_FORCE_MAX_ZONEORDER\x15
-CONFIG_ZBOOT_ROM_TEXT=0x0
-CONFIG_ZBOOT_ROM_BSS=0x0
-CONFIG_ARM_APPENDED_DTB=y
-CONFIG_KEXEC=y
-CONFIG_VFP=y
-# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
-CONFIG_PM=y
-CONFIG_PM_RUNTIME=y
-CONFIG_NET=y
-CONFIG_PACKET=y
-CONFIG_UNIX=y
-CONFIG_INET=y
-CONFIG_IP_MULTICAST=y
-CONFIG_IP_PNP=y
-CONFIG_IP_PNP_DHCP=y
-# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
-# CONFIG_INET_XFRM_MODE_TUNNEL is not set
-# CONFIG_INET_XFRM_MODE_BEET is not set
-# CONFIG_IPV6 is not set
-# CONFIG_WIRELESS is not set
-CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
-# CONFIG_FIRMWARE_IN_KERNEL is not set
-CONFIG_MTD=y
-CONFIG_MTD_CONCAT=y
-CONFIG_MTD_PARTITIONS=y
-CONFIG_MTD_CHAR=y
-CONFIG_MTD_BLOCK=y
-CONFIG_MTD_CFI=y
-CONFIG_MTD_CFI_ADV_OPTIONS=y
-CONFIG_MTD_CFI_INTELEXT=y
-CONFIG_MTD_PHYSMAP=y
-CONFIG_MTD_ARM_INTEGRATOR=y
-CONFIG_MTD_BLOCK2MTD=y
-CONFIG_SCSI=y
-CONFIG_BLK_DEV_SD=y
-# CONFIG_SCSI_LOWLEVEL is not set
-CONFIG_NETDEVICES=y
-CONFIG_NET_ETHERNET=y
-CONFIG_SMSC911X=y
-# CONFIG_NETDEV_1000 is not set
-# CONFIG_NETDEV_10000 is not set
-# CONFIG_WLAN is not set
-# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
-# CONFIG_INPUT_KEYBOARD is not set
-# CONFIG_INPUT_MOUSE is not set
-CONFIG_SERIAL_SH_SCI=y
-CONFIG_SERIAL_SH_SCI_NR_UARTS=8
-CONFIG_SERIAL_SH_SCI_CONSOLE=y
-# CONFIG_LEGACY_PTYS is not set
-# CONFIG_HW_RANDOM is not set
-CONFIG_I2C=y
-CONFIG_I2C_SH_MOBILE=y
-# CONFIG_HWMON is not set
-# CONFIG_MFD_SUPPORT is not set
-CONFIG_REGULATOR=y
-CONFIG_FB=y
-CONFIG_FB_MODE_HELPERS=y
-CONFIG_FB_SH_MOBILE_LCDC=y
-CONFIG_FB_SH_MOBILE_HDMI=y
-CONFIG_FRAMEBUFFER_CONSOLE=y
-CONFIG_LOGO=y
-# CONFIG_LOGO_LINUX_MONO is not set
-# CONFIG_LOGO_LINUX_CLUT224 is not set
-# CONFIG_SND_SUPPORT_OLD_API is not set
-# CONFIG_SND_VERBOSE_PROCFS is not set
-# CONFIG_SND_DRIVERS is not set
-# CONFIG_SND_ARM is not set
-CONFIG_SND_SOC_SH4_FSI=y
-CONFIG_USB=y
-CONFIG_USB_RENESAS_USBHS_HCD=y
-CONFIG_USB_RENESAS_USBHS=y
-CONFIG_USB_STORAGE=y
-CONFIG_USB_GADGET=y
-CONFIG_USB_RENESAS_USBHS_UDC=y
-CONFIG_MMC=y
-CONFIG_MMC_SDHI=y
-CONFIG_MMC_SH_MMCIF=y
-CONFIG_DMADEVICES=y
-CONFIG_SH_DMAE=y
-CONFIG_EXT2_FS=y
-CONFIG_EXT2_FS_XATTR=y
-CONFIG_EXT2_FS_POSIX_ACL=y
-CONFIG_EXT2_FS_SECURITY=y
-CONFIG_EXT2_FS_XIP=y
-CONFIG_EXT3_FS=y
-# CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set
-CONFIG_EXT3_FS_POSIX_ACL=y
-CONFIG_EXT3_FS_SECURITY=y
-# CONFIG_DNOTIFY is not set
-CONFIG_MSDOS_FS=y
-CONFIG_VFAT_FS=y
-CONFIG_TMPFS=y
-# CONFIG_MISC_FILESYSTEMS is not set
-CONFIG_NFS_FS=y
-CONFIG_NFS_V3=y
-CONFIG_NFS_V3_ACL=y
-CONFIG_NFS_V4=y
-CONFIG_NFS_V4_1=y
-CONFIG_ROOT_NFS=y
-CONFIG_NLS_CODEPAGE_437=y
-CONFIG_NLS_CODEPAGE_737=y
-CONFIG_NLS_CODEPAGE_775=y
-CONFIG_NLS_CODEPAGE_850=y
-CONFIG_NLS_CODEPAGE_852=y
-CONFIG_NLS_CODEPAGE_855=y
-CONFIG_NLS_CODEPAGE_857=y
-CONFIG_NLS_CODEPAGE_860=y
-CONFIG_NLS_CODEPAGE_861=y
-CONFIG_NLS_CODEPAGE_862=y
-CONFIG_NLS_CODEPAGE_863=y
-CONFIG_NLS_CODEPAGE_864=y
-CONFIG_NLS_CODEPAGE_865=y
-CONFIG_NLS_CODEPAGE_866=y
-CONFIG_NLS_CODEPAGE_869=y
-CONFIG_NLS_ISO8859_1=y
-CONFIG_NLS_ISO8859_2=y
-CONFIG_NLS_ISO8859_3=y
-CONFIG_NLS_ISO8859_4=y
-CONFIG_NLS_ISO8859_5=y
-CONFIG_NLS_ISO8859_6=y
-CONFIG_NLS_ISO8859_7=y
-CONFIG_NLS_ISO8859_9=y
-CONFIG_NLS_ISO8859_13=y
-CONFIG_NLS_ISO8859_14=y
-CONFIG_NLS_ISO8859_15=y
-CONFIG_NLS_KOI8_R=y
-CONFIG_NLS_KOI8_U=y
-CONFIG_NLS_UTF8=y
-# CONFIG_ENABLE_WARN_DEPRECATED is not set
-# CONFIG_ENABLE_MUST_CHECK is not set
-# CONFIG_ARM_UNWIND is not set
-CONFIG_CRYPTO=y
-CONFIG_CRYPTO_ANSI_CPRNG=y
--
1.7.10.4
^ permalink raw reply related [flat|nested] 38+ messages in thread
* [RFC/PATCH 7/7] ARM: shmobile: defconfig: Remove mackerel defconfig
@ 2013-04-04 3:29 ` Simon Horman
0 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-04 3:29 UTC (permalink / raw)
To: linux-arm-kernel
Remove mackerel defconfig as the shmobile defconfig may now be used instead.
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
arch/arm/configs/mackerel_defconfig | 156 -----------------------------------
1 file changed, 156 deletions(-)
delete mode 100644 arch/arm/configs/mackerel_defconfig
diff --git a/arch/arm/configs/mackerel_defconfig b/arch/arm/configs/mackerel_defconfig
deleted file mode 100644
index 9fb1189..0000000
--- a/arch/arm/configs/mackerel_defconfig
+++ /dev/null
@@ -1,156 +0,0 @@
-CONFIG_EXPERIMENTAL=y
-CONFIG_SYSVIPC=y
-CONFIG_IKCONFIG=y
-CONFIG_IKCONFIG_PROC=y
-CONFIG_LOG_BUF_SHIFT=16
-# CONFIG_UTS_NS is not set
-# CONFIG_IPC_NS is not set
-# CONFIG_USER_NS is not set
-# CONFIG_PID_NS is not set
-# CONFIG_NET_NS is not set
-CONFIG_SLAB=y
-CONFIG_MODULES=y
-CONFIG_MODULE_UNLOAD=y
-# CONFIG_BLK_DEV_BSG is not set
-# CONFIG_IOSCHED_DEADLINE is not set
-# CONFIG_IOSCHED_CFQ is not set
-CONFIG_ARCH_SHMOBILE=y
-CONFIG_ARCH_SH7372=y
-CONFIG_MACH_MACKEREL=y
-CONFIG_MEMORY_SIZE=0x10000000
-CONFIG_AEABI=y
-# CONFIG_OABI_COMPAT is not set
-CONFIG_FORCE_MAX_ZONEORDER=15
-CONFIG_ZBOOT_ROM_TEXT=0x0
-CONFIG_ZBOOT_ROM_BSS=0x0
-CONFIG_ARM_APPENDED_DTB=y
-CONFIG_KEXEC=y
-CONFIG_VFP=y
-# CONFIG_CORE_DUMP_DEFAULT_ELF_HEADERS is not set
-CONFIG_PM=y
-CONFIG_PM_RUNTIME=y
-CONFIG_NET=y
-CONFIG_PACKET=y
-CONFIG_UNIX=y
-CONFIG_INET=y
-CONFIG_IP_MULTICAST=y
-CONFIG_IP_PNP=y
-CONFIG_IP_PNP_DHCP=y
-# CONFIG_INET_XFRM_MODE_TRANSPORT is not set
-# CONFIG_INET_XFRM_MODE_TUNNEL is not set
-# CONFIG_INET_XFRM_MODE_BEET is not set
-# CONFIG_IPV6 is not set
-# CONFIG_WIRELESS is not set
-CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
-# CONFIG_FIRMWARE_IN_KERNEL is not set
-CONFIG_MTD=y
-CONFIG_MTD_CONCAT=y
-CONFIG_MTD_PARTITIONS=y
-CONFIG_MTD_CHAR=y
-CONFIG_MTD_BLOCK=y
-CONFIG_MTD_CFI=y
-CONFIG_MTD_CFI_ADV_OPTIONS=y
-CONFIG_MTD_CFI_INTELEXT=y
-CONFIG_MTD_PHYSMAP=y
-CONFIG_MTD_ARM_INTEGRATOR=y
-CONFIG_MTD_BLOCK2MTD=y
-CONFIG_SCSI=y
-CONFIG_BLK_DEV_SD=y
-# CONFIG_SCSI_LOWLEVEL is not set
-CONFIG_NETDEVICES=y
-CONFIG_NET_ETHERNET=y
-CONFIG_SMSC911X=y
-# CONFIG_NETDEV_1000 is not set
-# CONFIG_NETDEV_10000 is not set
-# CONFIG_WLAN is not set
-# CONFIG_INPUT_MOUSEDEV_PSAUX is not set
-# CONFIG_INPUT_KEYBOARD is not set
-# CONFIG_INPUT_MOUSE is not set
-CONFIG_SERIAL_SH_SCI=y
-CONFIG_SERIAL_SH_SCI_NR_UARTS=8
-CONFIG_SERIAL_SH_SCI_CONSOLE=y
-# CONFIG_LEGACY_PTYS is not set
-# CONFIG_HW_RANDOM is not set
-CONFIG_I2C=y
-CONFIG_I2C_SH_MOBILE=y
-# CONFIG_HWMON is not set
-# CONFIG_MFD_SUPPORT is not set
-CONFIG_REGULATOR=y
-CONFIG_FB=y
-CONFIG_FB_MODE_HELPERS=y
-CONFIG_FB_SH_MOBILE_LCDC=y
-CONFIG_FB_SH_MOBILE_HDMI=y
-CONFIG_FRAMEBUFFER_CONSOLE=y
-CONFIG_LOGO=y
-# CONFIG_LOGO_LINUX_MONO is not set
-# CONFIG_LOGO_LINUX_CLUT224 is not set
-# CONFIG_SND_SUPPORT_OLD_API is not set
-# CONFIG_SND_VERBOSE_PROCFS is not set
-# CONFIG_SND_DRIVERS is not set
-# CONFIG_SND_ARM is not set
-CONFIG_SND_SOC_SH4_FSI=y
-CONFIG_USB=y
-CONFIG_USB_RENESAS_USBHS_HCD=y
-CONFIG_USB_RENESAS_USBHS=y
-CONFIG_USB_STORAGE=y
-CONFIG_USB_GADGET=y
-CONFIG_USB_RENESAS_USBHS_UDC=y
-CONFIG_MMC=y
-CONFIG_MMC_SDHI=y
-CONFIG_MMC_SH_MMCIF=y
-CONFIG_DMADEVICES=y
-CONFIG_SH_DMAE=y
-CONFIG_EXT2_FS=y
-CONFIG_EXT2_FS_XATTR=y
-CONFIG_EXT2_FS_POSIX_ACL=y
-CONFIG_EXT2_FS_SECURITY=y
-CONFIG_EXT2_FS_XIP=y
-CONFIG_EXT3_FS=y
-# CONFIG_EXT3_DEFAULTS_TO_ORDERED is not set
-CONFIG_EXT3_FS_POSIX_ACL=y
-CONFIG_EXT3_FS_SECURITY=y
-# CONFIG_DNOTIFY is not set
-CONFIG_MSDOS_FS=y
-CONFIG_VFAT_FS=y
-CONFIG_TMPFS=y
-# CONFIG_MISC_FILESYSTEMS is not set
-CONFIG_NFS_FS=y
-CONFIG_NFS_V3=y
-CONFIG_NFS_V3_ACL=y
-CONFIG_NFS_V4=y
-CONFIG_NFS_V4_1=y
-CONFIG_ROOT_NFS=y
-CONFIG_NLS_CODEPAGE_437=y
-CONFIG_NLS_CODEPAGE_737=y
-CONFIG_NLS_CODEPAGE_775=y
-CONFIG_NLS_CODEPAGE_850=y
-CONFIG_NLS_CODEPAGE_852=y
-CONFIG_NLS_CODEPAGE_855=y
-CONFIG_NLS_CODEPAGE_857=y
-CONFIG_NLS_CODEPAGE_860=y
-CONFIG_NLS_CODEPAGE_861=y
-CONFIG_NLS_CODEPAGE_862=y
-CONFIG_NLS_CODEPAGE_863=y
-CONFIG_NLS_CODEPAGE_864=y
-CONFIG_NLS_CODEPAGE_865=y
-CONFIG_NLS_CODEPAGE_866=y
-CONFIG_NLS_CODEPAGE_869=y
-CONFIG_NLS_ISO8859_1=y
-CONFIG_NLS_ISO8859_2=y
-CONFIG_NLS_ISO8859_3=y
-CONFIG_NLS_ISO8859_4=y
-CONFIG_NLS_ISO8859_5=y
-CONFIG_NLS_ISO8859_6=y
-CONFIG_NLS_ISO8859_7=y
-CONFIG_NLS_ISO8859_9=y
-CONFIG_NLS_ISO8859_13=y
-CONFIG_NLS_ISO8859_14=y
-CONFIG_NLS_ISO8859_15=y
-CONFIG_NLS_KOI8_R=y
-CONFIG_NLS_KOI8_U=y
-CONFIG_NLS_UTF8=y
-# CONFIG_ENABLE_WARN_DEPRECATED is not set
-# CONFIG_ENABLE_MUST_CHECK is not set
-# CONFIG_ARM_UNWIND is not set
-CONFIG_CRYPTO=y
-CONFIG_CRYPTO_ANSI_CPRNG=y
--
1.7.10.4
^ permalink raw reply related [flat|nested] 38+ messages in thread
* [RFC/PATCH 8/7] ARCH: shmobile: defconfig consolidation (repost)
2013-04-04 3:29 ` Simon Horman
@ 2013-04-04 7:46 ` Simon Horman
-1 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-04 7:46 UTC (permalink / raw)
To: linux-arm-kernel
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
arch/arm/configs/shmobile_defconfig | 2 ++
1 file changed, 2 insertions(+)
Reposted with correct In-Reply-To header (hopefully!)
diff --git a/arch/arm/configs/shmobile_defconfig b/arch/arm/configs/shmobile_defconfig
index 9b6219a..7dba53f 100644
--- a/arch/arm/configs/shmobile_defconfig
+++ b/arch/arm/configs/shmobile_defconfig
@@ -14,9 +14,11 @@ CONFIG_SLAB=y
CONFIG_ARCH_SHMOBILE=y
CONFIG_ARCH_SH7372=y
CONFIG_ARCH_R8A7740=y
+CONFIG_ARCH_R8A7790=y
CONFIG_ARCH_EMEV2=y
CONFIG_MACH_MACKEREL=y
CONFIG_MACH_ARMADILLO800EVA=y
+CONFIG_MACH_LAGER=y
CONFIG_MACH_KZM9D=y
# CONFIG_SH_TIMER_TMU is not set
# CONFIG_SWP_EMULATE is not set
--
1.7.10.4
^ permalink raw reply related [flat|nested] 38+ messages in thread
* [RFC/PATCH 8/7] ARCH: shmobile: defconfig consolidation (repost)
@ 2013-04-04 7:46 ` Simon Horman
0 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-04 7:46 UTC (permalink / raw)
To: linux-arm-kernel
Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
---
arch/arm/configs/shmobile_defconfig | 2 ++
1 file changed, 2 insertions(+)
Reposted with correct In-Reply-To header (hopefully!)
diff --git a/arch/arm/configs/shmobile_defconfig b/arch/arm/configs/shmobile_defconfig
index 9b6219a..7dba53f 100644
--- a/arch/arm/configs/shmobile_defconfig
+++ b/arch/arm/configs/shmobile_defconfig
@@ -14,9 +14,11 @@ CONFIG_SLAB=y
CONFIG_ARCH_SHMOBILE=y
CONFIG_ARCH_SH7372=y
CONFIG_ARCH_R8A7740=y
+CONFIG_ARCH_R8A7790=y
CONFIG_ARCH_EMEV2=y
CONFIG_MACH_MACKEREL=y
CONFIG_MACH_ARMADILLO800EVA=y
+CONFIG_MACH_LAGER=y
CONFIG_MACH_KZM9D=y
# CONFIG_SH_TIMER_TMU is not set
# CONFIG_SWP_EMULATE is not set
--
1.7.10.4
^ permalink raw reply related [flat|nested] 38+ messages in thread
* Re: [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
2013-04-04 3:29 ` Simon Horman
@ 2013-04-04 11:20 ` Laurent Pinchart
-1 siblings, 0 replies; 38+ messages in thread
From: Laurent Pinchart @ 2013-04-04 11:20 UTC (permalink / raw)
To: linux-arm-kernel
Hi Simon,
On Thursday 04 April 2013 12:29:46 Simon Horman wrote:
> Hi,
>
> this is a first pass at consolidating the defconfigs of shmobile.
>
> It covers the mackerel, amradillo800eva and kzm9d boards which meet
> the following criteria:
>
> * Have the same base memory address (0x40000000).
Do you know if there's any work being done on getting rid of the base memory
address as a kernel config option ? It seriously hinders cross-SoC kernel
testing.
> * Work with RUNTIME_PM, it is desirable to have that a common defconfig
> * Are booted via DT, enabling the command line to be supplied in the dts.
> This is important to allow serial console and early printk settings,
> which vary wildly between boards, to be supplied.
> * Boards I have to test.
> This didn't eliminate any candidates that met the above criteria.
>
> I believe it should also be possible to add support for the APE6EVM
> board to the consolidated defconfig once problems with RUNTIME_PM
> have been isolated and resolved. I have send an email about this
> in a separate thread "APE6EVM and Runtime PM".
>
> I believe it may be possible to add support for the lager board
> to the consolidated defconfig once I am able to bring that board up,
> which should be rather soon. The lager board does not currently
> have a defconfig.
>
> Morimoto-san, I suspect it may be possible to add support for the
> bockw board to the consolidated defconfig if its boot loader supports
> booting using a zImage. In this case even though the base memory address
> is not the same as the boards above it should be possible to specify
> the base address from the boot loader. As I do not have a bockw board
> I am wondering if you could investigate this.
>
> Simon Horman (7):
> ARM: shmobile: prune defconfig
> ARM: shmobile: make defconfig canonical
> ARM: shmobile: Add kzm9d to consolidated defconfig
> ARM: shmobile: Add mackerel to consolidated defconfig
> ARM: shmobile: defconfig: Remove armadillo800eva defconfig
> ARM: shmobile: defconfig: Remove kzm9d defconfig
> ARM: shmobile: defconfig: Remove mackerel defconfig
>
> arch/arm/configs/armadillo800eva_defconfig | 153 -------------------------
> arch/arm/configs/kzm9d_defconfig | 88 ----------------
> arch/arm/configs/mackerel_defconfig | 156 -------------------------
> arch/arm/configs/shmobile_defconfig | 51 +++++----
> 4 files changed, 28 insertions(+), 420 deletions(-)
> delete mode 100644 arch/arm/configs/armadillo800eva_defconfig
> delete mode 100644 arch/arm/configs/kzm9d_defconfig
> delete mode 100644 arch/arm/configs/mackerel_defconfig
--
Regards,
Laurent Pinchart
^ permalink raw reply [flat|nested] 38+ messages in thread
* [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
@ 2013-04-04 11:20 ` Laurent Pinchart
0 siblings, 0 replies; 38+ messages in thread
From: Laurent Pinchart @ 2013-04-04 11:20 UTC (permalink / raw)
To: linux-arm-kernel
Hi Simon,
On Thursday 04 April 2013 12:29:46 Simon Horman wrote:
> Hi,
>
> this is a first pass at consolidating the defconfigs of shmobile.
>
> It covers the mackerel, amradillo800eva and kzm9d boards which meet
> the following criteria:
>
> * Have the same base memory address (0x40000000).
Do you know if there's any work being done on getting rid of the base memory
address as a kernel config option ? It seriously hinders cross-SoC kernel
testing.
> * Work with RUNTIME_PM, it is desirable to have that a common defconfig
> * Are booted via DT, enabling the command line to be supplied in the dts.
> This is important to allow serial console and early printk settings,
> which vary wildly between boards, to be supplied.
> * Boards I have to test.
> This didn't eliminate any candidates that met the above criteria.
>
> I believe it should also be possible to add support for the APE6EVM
> board to the consolidated defconfig once problems with RUNTIME_PM
> have been isolated and resolved. I have send an email about this
> in a separate thread "APE6EVM and Runtime PM".
>
> I believe it may be possible to add support for the lager board
> to the consolidated defconfig once I am able to bring that board up,
> which should be rather soon. The lager board does not currently
> have a defconfig.
>
> Morimoto-san, I suspect it may be possible to add support for the
> bockw board to the consolidated defconfig if its boot loader supports
> booting using a zImage. In this case even though the base memory address
> is not the same as the boards above it should be possible to specify
> the base address from the boot loader. As I do not have a bockw board
> I am wondering if you could investigate this.
>
> Simon Horman (7):
> ARM: shmobile: prune defconfig
> ARM: shmobile: make defconfig canonical
> ARM: shmobile: Add kzm9d to consolidated defconfig
> ARM: shmobile: Add mackerel to consolidated defconfig
> ARM: shmobile: defconfig: Remove armadillo800eva defconfig
> ARM: shmobile: defconfig: Remove kzm9d defconfig
> ARM: shmobile: defconfig: Remove mackerel defconfig
>
> arch/arm/configs/armadillo800eva_defconfig | 153 -------------------------
> arch/arm/configs/kzm9d_defconfig | 88 ----------------
> arch/arm/configs/mackerel_defconfig | 156 -------------------------
> arch/arm/configs/shmobile_defconfig | 51 +++++----
> 4 files changed, 28 insertions(+), 420 deletions(-)
> delete mode 100644 arch/arm/configs/armadillo800eva_defconfig
> delete mode 100644 arch/arm/configs/kzm9d_defconfig
> delete mode 100644 arch/arm/configs/mackerel_defconfig
--
Regards,
Laurent Pinchart
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
2013-04-04 11:20 ` Laurent Pinchart
@ 2013-04-05 0:30 ` Simon Horman
-1 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-05 0:30 UTC (permalink / raw)
To: linux-arm-kernel
On Thu, Apr 04, 2013 at 01:20:44PM +0200, Laurent Pinchart wrote:
> Hi Simon,
>
> On Thursday 04 April 2013 12:29:46 Simon Horman wrote:
> > Hi,
> >
> > this is a first pass at consolidating the defconfigs of shmobile.
> >
> > It covers the mackerel, amradillo800eva and kzm9d boards which meet
> > the following criteria:
> >
> > * Have the same base memory address (0x40000000).
>
> Do you know if there's any work being done on getting rid of the base memory
> address as a kernel config option ? It seriously hinders cross-SoC kernel
> testing.
As I understand things the main limitation is uImage which uses
the base memory address. There is some talk of creating uImages
at install time rather than build time. Which I believe would
remove most if not all the problem. However, its entirely unclear
to me what such an install process would look like. A new build target?
In tree script? Out of tree script? It seems very undefined to me.
Another, arguably better though not backwards compatible, option
is to boot using zImage (or even just Image) which do not rely
on the base address.
I'm not aware of any other work or discussion in this area although
it would not surprise me if there was some.
> > * Work with RUNTIME_PM, it is desirable to have that a common defconfig
> > * Are booted via DT, enabling the command line to be supplied in the dts.
> > This is important to allow serial console and early printk settings,
> > which vary wildly between boards, to be supplied.
> > * Boards I have to test.
> > This didn't eliminate any candidates that met the above criteria.
> >
> > I believe it should also be possible to add support for the APE6EVM
> > board to the consolidated defconfig once problems with RUNTIME_PM
> > have been isolated and resolved. I have send an email about this
> > in a separate thread "APE6EVM and Runtime PM".
> >
> > I believe it may be possible to add support for the lager board
> > to the consolidated defconfig once I am able to bring that board up,
> > which should be rather soon. The lager board does not currently
> > have a defconfig.
> >
> > Morimoto-san, I suspect it may be possible to add support for the
> > bockw board to the consolidated defconfig if its boot loader supports
> > booting using a zImage. In this case even though the base memory address
> > is not the same as the boards above it should be possible to specify
> > the base address from the boot loader. As I do not have a bockw board
> > I am wondering if you could investigate this.
> >
> > Simon Horman (7):
> > ARM: shmobile: prune defconfig
> > ARM: shmobile: make defconfig canonical
> > ARM: shmobile: Add kzm9d to consolidated defconfig
> > ARM: shmobile: Add mackerel to consolidated defconfig
> > ARM: shmobile: defconfig: Remove armadillo800eva defconfig
> > ARM: shmobile: defconfig: Remove kzm9d defconfig
> > ARM: shmobile: defconfig: Remove mackerel defconfig
> >
> > arch/arm/configs/armadillo800eva_defconfig | 153 -------------------------
> > arch/arm/configs/kzm9d_defconfig | 88 ----------------
> > arch/arm/configs/mackerel_defconfig | 156 -------------------------
> > arch/arm/configs/shmobile_defconfig | 51 +++++----
> > 4 files changed, 28 insertions(+), 420 deletions(-)
> > delete mode 100644 arch/arm/configs/armadillo800eva_defconfig
> > delete mode 100644 arch/arm/configs/kzm9d_defconfig
> > delete mode 100644 arch/arm/configs/mackerel_defconfig
> --
> Regards,
>
> Laurent Pinchart
>
^ permalink raw reply [flat|nested] 38+ messages in thread
* [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
@ 2013-04-05 0:30 ` Simon Horman
0 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-05 0:30 UTC (permalink / raw)
To: linux-arm-kernel
On Thu, Apr 04, 2013 at 01:20:44PM +0200, Laurent Pinchart wrote:
> Hi Simon,
>
> On Thursday 04 April 2013 12:29:46 Simon Horman wrote:
> > Hi,
> >
> > this is a first pass at consolidating the defconfigs of shmobile.
> >
> > It covers the mackerel, amradillo800eva and kzm9d boards which meet
> > the following criteria:
> >
> > * Have the same base memory address (0x40000000).
>
> Do you know if there's any work being done on getting rid of the base memory
> address as a kernel config option ? It seriously hinders cross-SoC kernel
> testing.
As I understand things the main limitation is uImage which uses
the base memory address. There is some talk of creating uImages
at install time rather than build time. Which I believe would
remove most if not all the problem. However, its entirely unclear
to me what such an install process would look like. A new build target?
In tree script? Out of tree script? It seems very undefined to me.
Another, arguably better though not backwards compatible, option
is to boot using zImage (or even just Image) which do not rely
on the base address.
I'm not aware of any other work or discussion in this area although
it would not surprise me if there was some.
> > * Work with RUNTIME_PM, it is desirable to have that a common defconfig
> > * Are booted via DT, enabling the command line to be supplied in the dts.
> > This is important to allow serial console and early printk settings,
> > which vary wildly between boards, to be supplied.
> > * Boards I have to test.
> > This didn't eliminate any candidates that met the above criteria.
> >
> > I believe it should also be possible to add support for the APE6EVM
> > board to the consolidated defconfig once problems with RUNTIME_PM
> > have been isolated and resolved. I have send an email about this
> > in a separate thread "APE6EVM and Runtime PM".
> >
> > I believe it may be possible to add support for the lager board
> > to the consolidated defconfig once I am able to bring that board up,
> > which should be rather soon. The lager board does not currently
> > have a defconfig.
> >
> > Morimoto-san, I suspect it may be possible to add support for the
> > bockw board to the consolidated defconfig if its boot loader supports
> > booting using a zImage. In this case even though the base memory address
> > is not the same as the boards above it should be possible to specify
> > the base address from the boot loader. As I do not have a bockw board
> > I am wondering if you could investigate this.
> >
> > Simon Horman (7):
> > ARM: shmobile: prune defconfig
> > ARM: shmobile: make defconfig canonical
> > ARM: shmobile: Add kzm9d to consolidated defconfig
> > ARM: shmobile: Add mackerel to consolidated defconfig
> > ARM: shmobile: defconfig: Remove armadillo800eva defconfig
> > ARM: shmobile: defconfig: Remove kzm9d defconfig
> > ARM: shmobile: defconfig: Remove mackerel defconfig
> >
> > arch/arm/configs/armadillo800eva_defconfig | 153 -------------------------
> > arch/arm/configs/kzm9d_defconfig | 88 ----------------
> > arch/arm/configs/mackerel_defconfig | 156 -------------------------
> > arch/arm/configs/shmobile_defconfig | 51 +++++----
> > 4 files changed, 28 insertions(+), 420 deletions(-)
> > delete mode 100644 arch/arm/configs/armadillo800eva_defconfig
> > delete mode 100644 arch/arm/configs/kzm9d_defconfig
> > delete mode 100644 arch/arm/configs/mackerel_defconfig
> --
> Regards,
>
> Laurent Pinchart
>
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
2013-04-05 0:30 ` Simon Horman
@ 2013-04-05 0:37 ` Laurent Pinchart
-1 siblings, 0 replies; 38+ messages in thread
From: Laurent Pinchart @ 2013-04-05 0:37 UTC (permalink / raw)
To: linux-arm-kernel
On Friday 05 April 2013 09:30:27 Simon Horman wrote:
> On Thu, Apr 04, 2013 at 01:20:44PM +0200, Laurent Pinchart wrote:
> > On Thursday 04 April 2013 12:29:46 Simon Horman wrote:
> > > Hi,
> > >
> > > this is a first pass at consolidating the defconfigs of shmobile.
> > >
> > > It covers the mackerel, amradillo800eva and kzm9d boards which meet
> > > the following criteria:
> > >
> > > * Have the same base memory address (0x40000000).
> >
> > Do you know if there's any work being done on getting rid of the base
> > memory address as a kernel config option ? It seriously hinders cross-SoC
> > kernel testing.
>
> As I understand things the main limitation is uImage which uses
> the base memory address. There is some talk of creating uImages
> at install time rather than build time. Which I believe would
> remove most if not all the problem. However, its entirely unclear
> to me what such an install process would look like. A new build target?
> In tree script? Out of tree script? It seems very undefined to me.
>
> Another, arguably better though not backwards compatible, option
> is to boot using zImage (or even just Image) which do not rely
> on the base address.
Don't we also need to get rid of CONFIG_MEMORY_START ? It's used in headsmp.S
and headsmp-scu.S (through PLAT_PHYS_OFFSET).
> I'm not aware of any other work or discussion in this area although
> it would not surprise me if there was some.
>
> > > * Work with RUNTIME_PM, it is desirable to have that a common defconfig
> > > * Are booted via DT, enabling the command line to be supplied in the
> > > dts.
> > >
> > > This is important to allow serial console and early printk settings,
> > > which vary wildly between boards, to be supplied.
> > >
> > > * Boards I have to test.
> > >
> > > This didn't eliminate any candidates that met the above criteria.
> > >
> > > I believe it should also be possible to add support for the APE6EVM
> > > board to the consolidated defconfig once problems with RUNTIME_PM
> > > have been isolated and resolved. I have send an email about this
> > > in a separate thread "APE6EVM and Runtime PM".
> > >
> > > I believe it may be possible to add support for the lager board
> > > to the consolidated defconfig once I am able to bring that board up,
> > > which should be rather soon. The lager board does not currently
> > > have a defconfig.
> > >
> > > Morimoto-san, I suspect it may be possible to add support for the
> > > bockw board to the consolidated defconfig if its boot loader supports
> > > booting using a zImage. In this case even though the base memory address
> > > is not the same as the boards above it should be possible to specify
> > > the base address from the boot loader. As I do not have a bockw board
> > > I am wondering if you could investigate this.
> > >
> > > Simon Horman (7):
> > > ARM: shmobile: prune defconfig
> > > ARM: shmobile: make defconfig canonical
> > > ARM: shmobile: Add kzm9d to consolidated defconfig
> > > ARM: shmobile: Add mackerel to consolidated defconfig
> > > ARM: shmobile: defconfig: Remove armadillo800eva defconfig
> > > ARM: shmobile: defconfig: Remove kzm9d defconfig
> > > ARM: shmobile: defconfig: Remove mackerel defconfig
> > >
> > > arch/arm/configs/armadillo800eva_defconfig | 153 ---------------------
> > > arch/arm/configs/kzm9d_defconfig | 88 ----------------
> > > arch/arm/configs/mackerel_defconfig | 156 ---------------------
> > > arch/arm/configs/shmobile_defconfig | 51 +++++----
> > > 4 files changed, 28 insertions(+), 420 deletions(-)
> > > delete mode 100644 arch/arm/configs/armadillo800eva_defconfig
> > > delete mode 100644 arch/arm/configs/kzm9d_defconfig
> > > delete mode 100644 arch/arm/configs/mackerel_defconfig
--
Regards,
Laurent Pinchart
^ permalink raw reply [flat|nested] 38+ messages in thread
* [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
@ 2013-04-05 0:37 ` Laurent Pinchart
0 siblings, 0 replies; 38+ messages in thread
From: Laurent Pinchart @ 2013-04-05 0:37 UTC (permalink / raw)
To: linux-arm-kernel
On Friday 05 April 2013 09:30:27 Simon Horman wrote:
> On Thu, Apr 04, 2013 at 01:20:44PM +0200, Laurent Pinchart wrote:
> > On Thursday 04 April 2013 12:29:46 Simon Horman wrote:
> > > Hi,
> > >
> > > this is a first pass at consolidating the defconfigs of shmobile.
> > >
> > > It covers the mackerel, amradillo800eva and kzm9d boards which meet
> > > the following criteria:
> > >
> > > * Have the same base memory address (0x40000000).
> >
> > Do you know if there's any work being done on getting rid of the base
> > memory address as a kernel config option ? It seriously hinders cross-SoC
> > kernel testing.
>
> As I understand things the main limitation is uImage which uses
> the base memory address. There is some talk of creating uImages
> at install time rather than build time. Which I believe would
> remove most if not all the problem. However, its entirely unclear
> to me what such an install process would look like. A new build target?
> In tree script? Out of tree script? It seems very undefined to me.
>
> Another, arguably better though not backwards compatible, option
> is to boot using zImage (or even just Image) which do not rely
> on the base address.
Don't we also need to get rid of CONFIG_MEMORY_START ? It's used in headsmp.S
and headsmp-scu.S (through PLAT_PHYS_OFFSET).
> I'm not aware of any other work or discussion in this area although
> it would not surprise me if there was some.
>
> > > * Work with RUNTIME_PM, it is desirable to have that a common defconfig
> > > * Are booted via DT, enabling the command line to be supplied in the
> > > dts.
> > >
> > > This is important to allow serial console and early printk settings,
> > > which vary wildly between boards, to be supplied.
> > >
> > > * Boards I have to test.
> > >
> > > This didn't eliminate any candidates that met the above criteria.
> > >
> > > I believe it should also be possible to add support for the APE6EVM
> > > board to the consolidated defconfig once problems with RUNTIME_PM
> > > have been isolated and resolved. I have send an email about this
> > > in a separate thread "APE6EVM and Runtime PM".
> > >
> > > I believe it may be possible to add support for the lager board
> > > to the consolidated defconfig once I am able to bring that board up,
> > > which should be rather soon. The lager board does not currently
> > > have a defconfig.
> > >
> > > Morimoto-san, I suspect it may be possible to add support for the
> > > bockw board to the consolidated defconfig if its boot loader supports
> > > booting using a zImage. In this case even though the base memory address
> > > is not the same as the boards above it should be possible to specify
> > > the base address from the boot loader. As I do not have a bockw board
> > > I am wondering if you could investigate this.
> > >
> > > Simon Horman (7):
> > > ARM: shmobile: prune defconfig
> > > ARM: shmobile: make defconfig canonical
> > > ARM: shmobile: Add kzm9d to consolidated defconfig
> > > ARM: shmobile: Add mackerel to consolidated defconfig
> > > ARM: shmobile: defconfig: Remove armadillo800eva defconfig
> > > ARM: shmobile: defconfig: Remove kzm9d defconfig
> > > ARM: shmobile: defconfig: Remove mackerel defconfig
> > >
> > > arch/arm/configs/armadillo800eva_defconfig | 153 ---------------------
> > > arch/arm/configs/kzm9d_defconfig | 88 ----------------
> > > arch/arm/configs/mackerel_defconfig | 156 ---------------------
> > > arch/arm/configs/shmobile_defconfig | 51 +++++----
> > > 4 files changed, 28 insertions(+), 420 deletions(-)
> > > delete mode 100644 arch/arm/configs/armadillo800eva_defconfig
> > > delete mode 100644 arch/arm/configs/kzm9d_defconfig
> > > delete mode 100644 arch/arm/configs/mackerel_defconfig
--
Regards,
Laurent Pinchart
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
2013-04-05 0:37 ` Laurent Pinchart
@ 2013-04-05 0:49 ` Simon Horman
-1 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-05 0:49 UTC (permalink / raw)
To: linux-arm-kernel
On Fri, Apr 05, 2013 at 02:37:38AM +0200, Laurent Pinchart wrote:
> On Friday 05 April 2013 09:30:27 Simon Horman wrote:
> > On Thu, Apr 04, 2013 at 01:20:44PM +0200, Laurent Pinchart wrote:
> > > On Thursday 04 April 2013 12:29:46 Simon Horman wrote:
> > > > Hi,
> > > >
> > > > this is a first pass at consolidating the defconfigs of shmobile.
> > > >
> > > > It covers the mackerel, amradillo800eva and kzm9d boards which meet
> > > > the following criteria:
> > > >
> > > > * Have the same base memory address (0x40000000).
> > >
> > > Do you know if there's any work being done on getting rid of the base
> > > memory address as a kernel config option ? It seriously hinders cross-SoC
> > > kernel testing.
> >
> > As I understand things the main limitation is uImage which uses
> > the base memory address. There is some talk of creating uImages
> > at install time rather than build time. Which I believe would
> > remove most if not all the problem. However, its entirely unclear
> > to me what such an install process would look like. A new build target?
> > In tree script? Out of tree script? It seems very undefined to me.
> >
> > Another, arguably better though not backwards compatible, option
> > is to boot using zImage (or even just Image) which do not rely
> > on the base address.
>
> Don't we also need to get rid of CONFIG_MEMORY_START ? It's used in headsmp.S
> and headsmp-scu.S (through PLAT_PHYS_OFFSET).
Yes, I think so. Sorry for glossing over that.
I think it should be possible to remove that by evaluating it at runtime
somehow. But I have not though deeply about this.
> > I'm not aware of any other work or discussion in this area although
> > it would not surprise me if there was some.
> >
> > > > * Work with RUNTIME_PM, it is desirable to have that a common defconfig
> > > > * Are booted via DT, enabling the command line to be supplied in the
> > > > dts.
> > > >
> > > > This is important to allow serial console and early printk settings,
> > > > which vary wildly between boards, to be supplied.
> > > >
> > > > * Boards I have to test.
> > > >
> > > > This didn't eliminate any candidates that met the above criteria.
> > > >
> > > > I believe it should also be possible to add support for the APE6EVM
> > > > board to the consolidated defconfig once problems with RUNTIME_PM
> > > > have been isolated and resolved. I have send an email about this
> > > > in a separate thread "APE6EVM and Runtime PM".
> > > >
> > > > I believe it may be possible to add support for the lager board
> > > > to the consolidated defconfig once I am able to bring that board up,
> > > > which should be rather soon. The lager board does not currently
> > > > have a defconfig.
> > > >
> > > > Morimoto-san, I suspect it may be possible to add support for the
> > > > bockw board to the consolidated defconfig if its boot loader supports
> > > > booting using a zImage. In this case even though the base memory address
> > > > is not the same as the boards above it should be possible to specify
> > > > the base address from the boot loader. As I do not have a bockw board
> > > > I am wondering if you could investigate this.
> > > >
> > > > Simon Horman (7):
> > > > ARM: shmobile: prune defconfig
> > > > ARM: shmobile: make defconfig canonical
> > > > ARM: shmobile: Add kzm9d to consolidated defconfig
> > > > ARM: shmobile: Add mackerel to consolidated defconfig
> > > > ARM: shmobile: defconfig: Remove armadillo800eva defconfig
> > > > ARM: shmobile: defconfig: Remove kzm9d defconfig
> > > > ARM: shmobile: defconfig: Remove mackerel defconfig
> > > >
> > > > arch/arm/configs/armadillo800eva_defconfig | 153 ---------------------
> > > > arch/arm/configs/kzm9d_defconfig | 88 ----------------
> > > > arch/arm/configs/mackerel_defconfig | 156 ---------------------
> > > > arch/arm/configs/shmobile_defconfig | 51 +++++----
> > > > 4 files changed, 28 insertions(+), 420 deletions(-)
> > > > delete mode 100644 arch/arm/configs/armadillo800eva_defconfig
> > > > delete mode 100644 arch/arm/configs/kzm9d_defconfig
> > > > delete mode 100644 arch/arm/configs/mackerel_defconfig
^ permalink raw reply [flat|nested] 38+ messages in thread
* [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
@ 2013-04-05 0:49 ` Simon Horman
0 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-05 0:49 UTC (permalink / raw)
To: linux-arm-kernel
On Fri, Apr 05, 2013 at 02:37:38AM +0200, Laurent Pinchart wrote:
> On Friday 05 April 2013 09:30:27 Simon Horman wrote:
> > On Thu, Apr 04, 2013 at 01:20:44PM +0200, Laurent Pinchart wrote:
> > > On Thursday 04 April 2013 12:29:46 Simon Horman wrote:
> > > > Hi,
> > > >
> > > > this is a first pass at consolidating the defconfigs of shmobile.
> > > >
> > > > It covers the mackerel, amradillo800eva and kzm9d boards which meet
> > > > the following criteria:
> > > >
> > > > * Have the same base memory address (0x40000000).
> > >
> > > Do you know if there's any work being done on getting rid of the base
> > > memory address as a kernel config option ? It seriously hinders cross-SoC
> > > kernel testing.
> >
> > As I understand things the main limitation is uImage which uses
> > the base memory address. There is some talk of creating uImages
> > at install time rather than build time. Which I believe would
> > remove most if not all the problem. However, its entirely unclear
> > to me what such an install process would look like. A new build target?
> > In tree script? Out of tree script? It seems very undefined to me.
> >
> > Another, arguably better though not backwards compatible, option
> > is to boot using zImage (or even just Image) which do not rely
> > on the base address.
>
> Don't we also need to get rid of CONFIG_MEMORY_START ? It's used in headsmp.S
> and headsmp-scu.S (through PLAT_PHYS_OFFSET).
Yes, I think so. Sorry for glossing over that.
I think it should be possible to remove that by evaluating it at runtime
somehow. But I have not though deeply about this.
> > I'm not aware of any other work or discussion in this area although
> > it would not surprise me if there was some.
> >
> > > > * Work with RUNTIME_PM, it is desirable to have that a common defconfig
> > > > * Are booted via DT, enabling the command line to be supplied in the
> > > > dts.
> > > >
> > > > This is important to allow serial console and early printk settings,
> > > > which vary wildly between boards, to be supplied.
> > > >
> > > > * Boards I have to test.
> > > >
> > > > This didn't eliminate any candidates that met the above criteria.
> > > >
> > > > I believe it should also be possible to add support for the APE6EVM
> > > > board to the consolidated defconfig once problems with RUNTIME_PM
> > > > have been isolated and resolved. I have send an email about this
> > > > in a separate thread "APE6EVM and Runtime PM".
> > > >
> > > > I believe it may be possible to add support for the lager board
> > > > to the consolidated defconfig once I am able to bring that board up,
> > > > which should be rather soon. The lager board does not currently
> > > > have a defconfig.
> > > >
> > > > Morimoto-san, I suspect it may be possible to add support for the
> > > > bockw board to the consolidated defconfig if its boot loader supports
> > > > booting using a zImage. In this case even though the base memory address
> > > > is not the same as the boards above it should be possible to specify
> > > > the base address from the boot loader. As I do not have a bockw board
> > > > I am wondering if you could investigate this.
> > > >
> > > > Simon Horman (7):
> > > > ARM: shmobile: prune defconfig
> > > > ARM: shmobile: make defconfig canonical
> > > > ARM: shmobile: Add kzm9d to consolidated defconfig
> > > > ARM: shmobile: Add mackerel to consolidated defconfig
> > > > ARM: shmobile: defconfig: Remove armadillo800eva defconfig
> > > > ARM: shmobile: defconfig: Remove kzm9d defconfig
> > > > ARM: shmobile: defconfig: Remove mackerel defconfig
> > > >
> > > > arch/arm/configs/armadillo800eva_defconfig | 153 ---------------------
> > > > arch/arm/configs/kzm9d_defconfig | 88 ----------------
> > > > arch/arm/configs/mackerel_defconfig | 156 ---------------------
> > > > arch/arm/configs/shmobile_defconfig | 51 +++++----
> > > > 4 files changed, 28 insertions(+), 420 deletions(-)
> > > > delete mode 100644 arch/arm/configs/armadillo800eva_defconfig
> > > > delete mode 100644 arch/arm/configs/kzm9d_defconfig
> > > > delete mode 100644 arch/arm/configs/mackerel_defconfig
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
2013-04-04 3:29 ` Simon Horman
@ 2013-04-05 3:08 ` Simon Horman
-1 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-05 3:08 UTC (permalink / raw)
To: linux-arm-kernel
On Thu, Apr 04, 2013 at 12:29:46PM +0900, Simon Horman wrote:
> Hi,
>
> this is a first pass at consolidating the defconfigs of shmobile.
>
> It covers the mackerel, amradillo800eva and kzm9d boards which meet
> the following criteria:
>
> * Have the same base memory address (0x40000000).
> * Work with RUNTIME_PM, it is desirable to have that a common defconfig
> * Are booted via DT, enabling the command line to be supplied in the dts.
> This is important to allow serial console and early printk settings,
> which vary wildly between boards, to be supplied.
> * Boards I have to test.
> This didn't eliminate any candidates that met the above criteria.
>
> I believe it should also be possible to add support for the APE6EVM
> board to the consolidated defconfig once problems with RUNTIME_PM
> have been isolated and resolved. I have send an email about this
> in a separate thread "APE6EVM and Runtime PM".
>
> I believe it may be possible to add support for the lager board
> to the consolidated defconfig once I am able to bring that board up,
> which should be rather soon. The lager board does not currently
> have a defconfig.
>
> Morimoto-san, I suspect it may be possible to add support for the
> bockw board to the consolidated defconfig if its boot loader supports
> booting using a zImage. In this case even though the base memory address
> is not the same as the boards above it should be possible to specify
> the base address from the boot loader. As I do not have a bockw board
> I am wondering if you could investigate this.
>
> Simon Horman (7):
> ARM: shmobile: prune defconfig
> ARM: shmobile: make defconfig canonical
> ARM: shmobile: Add kzm9d to consolidated defconfig
> ARM: shmobile: Add mackerel to consolidated defconfig
> ARM: shmobile: defconfig: Remove armadillo800eva defconfig
> ARM: shmobile: defconfig: Remove kzm9d defconfig
> ARM: shmobile: defconfig: Remove mackerel defconfig
>
> arch/arm/configs/armadillo800eva_defconfig | 153 ---------------------------
> arch/arm/configs/kzm9d_defconfig | 88 ----------------
> arch/arm/configs/mackerel_defconfig | 156 ----------------------------
> arch/arm/configs/shmobile_defconfig | 51 +++++----
> 4 files changed, 28 insertions(+), 420 deletions(-)
> delete mode 100644 arch/arm/configs/armadillo800eva_defconfig
> delete mode 100644 arch/arm/configs/kzm9d_defconfig
> delete mode 100644 arch/arm/configs/mackerel_defconfig
Magnus,
ideally I would like to queue-up this series and request
it be included in v3.10 as a path to add defconfig support for the lager
baord (added as an 8th patch after my original posting of the series).
Can I get some feedback from you?
^ permalink raw reply [flat|nested] 38+ messages in thread
* [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
@ 2013-04-05 3:08 ` Simon Horman
0 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-05 3:08 UTC (permalink / raw)
To: linux-arm-kernel
On Thu, Apr 04, 2013 at 12:29:46PM +0900, Simon Horman wrote:
> Hi,
>
> this is a first pass at consolidating the defconfigs of shmobile.
>
> It covers the mackerel, amradillo800eva and kzm9d boards which meet
> the following criteria:
>
> * Have the same base memory address (0x40000000).
> * Work with RUNTIME_PM, it is desirable to have that a common defconfig
> * Are booted via DT, enabling the command line to be supplied in the dts.
> This is important to allow serial console and early printk settings,
> which vary wildly between boards, to be supplied.
> * Boards I have to test.
> This didn't eliminate any candidates that met the above criteria.
>
> I believe it should also be possible to add support for the APE6EVM
> board to the consolidated defconfig once problems with RUNTIME_PM
> have been isolated and resolved. I have send an email about this
> in a separate thread "APE6EVM and Runtime PM".
>
> I believe it may be possible to add support for the lager board
> to the consolidated defconfig once I am able to bring that board up,
> which should be rather soon. The lager board does not currently
> have a defconfig.
>
> Morimoto-san, I suspect it may be possible to add support for the
> bockw board to the consolidated defconfig if its boot loader supports
> booting using a zImage. In this case even though the base memory address
> is not the same as the boards above it should be possible to specify
> the base address from the boot loader. As I do not have a bockw board
> I am wondering if you could investigate this.
>
> Simon Horman (7):
> ARM: shmobile: prune defconfig
> ARM: shmobile: make defconfig canonical
> ARM: shmobile: Add kzm9d to consolidated defconfig
> ARM: shmobile: Add mackerel to consolidated defconfig
> ARM: shmobile: defconfig: Remove armadillo800eva defconfig
> ARM: shmobile: defconfig: Remove kzm9d defconfig
> ARM: shmobile: defconfig: Remove mackerel defconfig
>
> arch/arm/configs/armadillo800eva_defconfig | 153 ---------------------------
> arch/arm/configs/kzm9d_defconfig | 88 ----------------
> arch/arm/configs/mackerel_defconfig | 156 ----------------------------
> arch/arm/configs/shmobile_defconfig | 51 +++++----
> 4 files changed, 28 insertions(+), 420 deletions(-)
> delete mode 100644 arch/arm/configs/armadillo800eva_defconfig
> delete mode 100644 arch/arm/configs/kzm9d_defconfig
> delete mode 100644 arch/arm/configs/mackerel_defconfig
Magnus,
ideally I would like to queue-up this series and request
it be included in v3.10 as a path to add defconfig support for the lager
baord (added as an 8th patch after my original posting of the series).
Can I get some feedback from you?
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
2013-04-05 0:49 ` Simon Horman
@ 2013-04-05 10:07 ` Laurent Pinchart
-1 siblings, 0 replies; 38+ messages in thread
From: Laurent Pinchart @ 2013-04-05 10:07 UTC (permalink / raw)
To: linux-arm-kernel
Hi Simon,
On Friday 05 April 2013 09:49:31 Simon Horman wrote:
> On Fri, Apr 05, 2013 at 02:37:38AM +0200, Laurent Pinchart wrote:
> > On Friday 05 April 2013 09:30:27 Simon Horman wrote:
> > > On Thu, Apr 04, 2013 at 01:20:44PM +0200, Laurent Pinchart wrote:
> > > > On Thursday 04 April 2013 12:29:46 Simon Horman wrote:
> > > > > Hi,
> > > > >
> > > > > this is a first pass at consolidating the defconfigs of shmobile.
> > > > >
> > > > > It covers the mackerel, amradillo800eva and kzm9d boards which meet
> > > > > the following criteria:
> > > > >
> > > > > * Have the same base memory address (0x40000000).
> > > >
> > > > Do you know if there's any work being done on getting rid of the base
> > > > memory address as a kernel config option ? It seriously hinders
> > > > cross-SoC kernel testing.
> > >
> > > As I understand things the main limitation is uImage which uses
> > > the base memory address. There is some talk of creating uImages
> > > at install time rather than build time. Which I believe would
> > > remove most if not all the problem. However, its entirely unclear
> > > to me what such an install process would look like. A new build target?
> > > In tree script? Out of tree script? It seems very undefined to me.
> > >
> > > Another, arguably better though not backwards compatible, option
> > > is to boot using zImage (or even just Image) which do not rely
> > > on the base address.
> >
> > Don't we also need to get rid of CONFIG_MEMORY_START ? It's used in
> > headsmp.S and headsmp-scu.S (through PLAT_PHYS_OFFSET).
>
> Yes, I think so. Sorry for glossing over that.
>
> I think it should be possible to remove that by evaluating it at runtime
> somehow. But I have not though deeply about this.
It would be really nice if someone could give it a try :-)
--
Regards,
Laurent Pinchart
^ permalink raw reply [flat|nested] 38+ messages in thread
* [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
@ 2013-04-05 10:07 ` Laurent Pinchart
0 siblings, 0 replies; 38+ messages in thread
From: Laurent Pinchart @ 2013-04-05 10:07 UTC (permalink / raw)
To: linux-arm-kernel
Hi Simon,
On Friday 05 April 2013 09:49:31 Simon Horman wrote:
> On Fri, Apr 05, 2013 at 02:37:38AM +0200, Laurent Pinchart wrote:
> > On Friday 05 April 2013 09:30:27 Simon Horman wrote:
> > > On Thu, Apr 04, 2013 at 01:20:44PM +0200, Laurent Pinchart wrote:
> > > > On Thursday 04 April 2013 12:29:46 Simon Horman wrote:
> > > > > Hi,
> > > > >
> > > > > this is a first pass at consolidating the defconfigs of shmobile.
> > > > >
> > > > > It covers the mackerel, amradillo800eva and kzm9d boards which meet
> > > > > the following criteria:
> > > > >
> > > > > * Have the same base memory address (0x40000000).
> > > >
> > > > Do you know if there's any work being done on getting rid of the base
> > > > memory address as a kernel config option ? It seriously hinders
> > > > cross-SoC kernel testing.
> > >
> > > As I understand things the main limitation is uImage which uses
> > > the base memory address. There is some talk of creating uImages
> > > at install time rather than build time. Which I believe would
> > > remove most if not all the problem. However, its entirely unclear
> > > to me what such an install process would look like. A new build target?
> > > In tree script? Out of tree script? It seems very undefined to me.
> > >
> > > Another, arguably better though not backwards compatible, option
> > > is to boot using zImage (or even just Image) which do not rely
> > > on the base address.
> >
> > Don't we also need to get rid of CONFIG_MEMORY_START ? It's used in
> > headsmp.S and headsmp-scu.S (through PLAT_PHYS_OFFSET).
>
> Yes, I think so. Sorry for glossing over that.
>
> I think it should be possible to remove that by evaluating it at runtime
> somehow. But I have not though deeply about this.
It would be really nice if someone could give it a try :-)
--
Regards,
Laurent Pinchart
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
2013-04-04 3:29 ` Simon Horman
@ 2013-04-08 1:07 ` Kuninori Morimoto
-1 siblings, 0 replies; 38+ messages in thread
From: Kuninori Morimoto @ 2013-04-08 1:07 UTC (permalink / raw)
To: linux-arm-kernel
Hi Simon
> Simon Horman (7):
> ARM: shmobile: prune defconfig
> ARM: shmobile: make defconfig canonical
> ARM: shmobile: Add kzm9d to consolidated defconfig
> ARM: shmobile: Add mackerel to consolidated defconfig
> ARM: shmobile: defconfig: Remove armadillo800eva defconfig
> ARM: shmobile: defconfig: Remove kzm9d defconfig
> ARM: shmobile: defconfig: Remove mackerel defconfig
(snip)
> Morimoto-san, I suspect it may be possible to add support for the
> bockw board to the consolidated defconfig if its boot loader supports
> booting using a zImage. In this case even though the base memory address
> is not the same as the boards above it should be possible to specify
> the base address from the boot loader. As I do not have a bockw board
> I am wondering if you could investigate this.
I tested shmobile_defconfig on Bock-W board.
It works with...
1) I added R8A7778 SoC on .config
2) I added Bock-W on .config
3) I fixuped CONFIG_MEMORY_START, CONFIG_MEMORY_SIZE value on .config
It is correct method ?
Best regards
---
Kuninori Morimoto
^ permalink raw reply [flat|nested] 38+ messages in thread
* [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
@ 2013-04-08 1:07 ` Kuninori Morimoto
0 siblings, 0 replies; 38+ messages in thread
From: Kuninori Morimoto @ 2013-04-08 1:07 UTC (permalink / raw)
To: linux-arm-kernel
Hi Simon
> Simon Horman (7):
> ARM: shmobile: prune defconfig
> ARM: shmobile: make defconfig canonical
> ARM: shmobile: Add kzm9d to consolidated defconfig
> ARM: shmobile: Add mackerel to consolidated defconfig
> ARM: shmobile: defconfig: Remove armadillo800eva defconfig
> ARM: shmobile: defconfig: Remove kzm9d defconfig
> ARM: shmobile: defconfig: Remove mackerel defconfig
(snip)
> Morimoto-san, I suspect it may be possible to add support for the
> bockw board to the consolidated defconfig if its boot loader supports
> booting using a zImage. In this case even though the base memory address
> is not the same as the boards above it should be possible to specify
> the base address from the boot loader. As I do not have a bockw board
> I am wondering if you could investigate this.
I tested shmobile_defconfig on Bock-W board.
It works with...
1) I added R8A7778 SoC on .config
2) I added Bock-W on .config
3) I fixuped CONFIG_MEMORY_START, CONFIG_MEMORY_SIZE value on .config
It is correct method ?
Best regards
---
Kuninori Morimoto
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
2013-04-08 1:07 ` Kuninori Morimoto
@ 2013-04-08 2:16 ` Simon Horman
-1 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-08 2:16 UTC (permalink / raw)
To: linux-arm-kernel
On Sun, Apr 07, 2013 at 06:07:16PM -0700, Kuninori Morimoto wrote:
>
> Hi Simon
>
> > Simon Horman (7):
> > ARM: shmobile: prune defconfig
> > ARM: shmobile: make defconfig canonical
> > ARM: shmobile: Add kzm9d to consolidated defconfig
> > ARM: shmobile: Add mackerel to consolidated defconfig
> > ARM: shmobile: defconfig: Remove armadillo800eva defconfig
> > ARM: shmobile: defconfig: Remove kzm9d defconfig
> > ARM: shmobile: defconfig: Remove mackerel defconfig
> (snip)
> > Morimoto-san, I suspect it may be possible to add support for the
> > bockw board to the consolidated defconfig if its boot loader supports
> > booting using a zImage. In this case even though the base memory address
> > is not the same as the boards above it should be possible to specify
> > the base address from the boot loader. As I do not have a bockw board
> > I am wondering if you could investigate this.
>
> I tested shmobile_defconfig on Bock-W board.
> It works with...
>
> 1) I added R8A7778 SoC on .config
> 2) I added Bock-W on .config
> 3) I fixuped CONFIG_MEMORY_START, CONFIG_MEMORY_SIZE value on .config
>
> It is correct method ?
Unfortunately not, the idea is not to modify CONFIG_MEMORY_START
or CONFIG_MEMORY_SIZE.
My understanding is that if you load a zImage at the correct
start address (0x60000000 IIRC) and then execute it using bootz
then the kernel should relocate and run from that address.
^ permalink raw reply [flat|nested] 38+ messages in thread
* [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
@ 2013-04-08 2:16 ` Simon Horman
0 siblings, 0 replies; 38+ messages in thread
From: Simon Horman @ 2013-04-08 2:16 UTC (permalink / raw)
To: linux-arm-kernel
On Sun, Apr 07, 2013 at 06:07:16PM -0700, Kuninori Morimoto wrote:
>
> Hi Simon
>
> > Simon Horman (7):
> > ARM: shmobile: prune defconfig
> > ARM: shmobile: make defconfig canonical
> > ARM: shmobile: Add kzm9d to consolidated defconfig
> > ARM: shmobile: Add mackerel to consolidated defconfig
> > ARM: shmobile: defconfig: Remove armadillo800eva defconfig
> > ARM: shmobile: defconfig: Remove kzm9d defconfig
> > ARM: shmobile: defconfig: Remove mackerel defconfig
> (snip)
> > Morimoto-san, I suspect it may be possible to add support for the
> > bockw board to the consolidated defconfig if its boot loader supports
> > booting using a zImage. In this case even though the base memory address
> > is not the same as the boards above it should be possible to specify
> > the base address from the boot loader. As I do not have a bockw board
> > I am wondering if you could investigate this.
>
> I tested shmobile_defconfig on Bock-W board.
> It works with...
>
> 1) I added R8A7778 SoC on .config
> 2) I added Bock-W on .config
> 3) I fixuped CONFIG_MEMORY_START, CONFIG_MEMORY_SIZE value on .config
>
> It is correct method ?
Unfortunately not, the idea is not to modify CONFIG_MEMORY_START
or CONFIG_MEMORY_SIZE.
My understanding is that if you load a zImage at the correct
start address (0x60000000 IIRC) and then execute it using bootz
then the kernel should relocate and run from that address.
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
2013-04-08 2:16 ` Simon Horman
@ 2013-04-08 2:52 ` Kuninori Morimoto
-1 siblings, 0 replies; 38+ messages in thread
From: Kuninori Morimoto @ 2013-04-08 2:52 UTC (permalink / raw)
To: linux-arm-kernel
Hi Simon
> > > Morimoto-san, I suspect it may be possible to add support for the
> > > bockw board to the consolidated defconfig if its boot loader supports
> > > booting using a zImage. In this case even though the base memory address
> > > is not the same as the boards above it should be possible to specify
> > > the base address from the boot loader. As I do not have a bockw board
> > > I am wondering if you could investigate this.
> >
> > I tested shmobile_defconfig on Bock-W board.
> > It works with...
> >
> > 1) I added R8A7778 SoC on .config
> > 2) I added Bock-W on .config
> > 3) I fixuped CONFIG_MEMORY_START, CONFIG_MEMORY_SIZE value on .config
> >
> > It is correct method ?
>
> Unfortunately not, the idea is not to modify CONFIG_MEMORY_START
> or CONFIG_MEMORY_SIZE.
>
> My understanding is that if you load a zImage at the correct
> start address (0x60000000 IIRC) and then execute it using bootz
> then the kernel should relocate and run from that address.
Hmm...
This means 3) is not needed, but it didn't work without 3)
Is it R8A7778 or Bock-W DT code issue ?
Best regards
---
Kuninori Morimoto
^ permalink raw reply [flat|nested] 38+ messages in thread
* [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
@ 2013-04-08 2:52 ` Kuninori Morimoto
0 siblings, 0 replies; 38+ messages in thread
From: Kuninori Morimoto @ 2013-04-08 2:52 UTC (permalink / raw)
To: linux-arm-kernel
Hi Simon
> > > Morimoto-san, I suspect it may be possible to add support for the
> > > bockw board to the consolidated defconfig if its boot loader supports
> > > booting using a zImage. In this case even though the base memory address
> > > is not the same as the boards above it should be possible to specify
> > > the base address from the boot loader. As I do not have a bockw board
> > > I am wondering if you could investigate this.
> >
> > I tested shmobile_defconfig on Bock-W board.
> > It works with...
> >
> > 1) I added R8A7778 SoC on .config
> > 2) I added Bock-W on .config
> > 3) I fixuped CONFIG_MEMORY_START, CONFIG_MEMORY_SIZE value on .config
> >
> > It is correct method ?
>
> Unfortunately not, the idea is not to modify CONFIG_MEMORY_START
> or CONFIG_MEMORY_SIZE.
>
> My understanding is that if you load a zImage at the correct
> start address (0x60000000 IIRC) and then execute it using bootz
> then the kernel should relocate and run from that address.
Hmm...
This means 3) is not needed, but it didn't work without 3)
Is it R8A7778 or Bock-W DT code issue ?
Best regards
---
Kuninori Morimoto
^ permalink raw reply [flat|nested] 38+ messages in thread
* Re: [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
2013-04-08 2:52 ` Kuninori Morimoto
@ 2013-04-08 3:16 ` Kuninori Morimoto
-1 siblings, 0 replies; 38+ messages in thread
From: Kuninori Morimoto @ 2013-04-08 3:16 UTC (permalink / raw)
To: linux-arm-kernel
Hi Simon
> > Unfortunately not, the idea is not to modify CONFIG_MEMORY_START
> > or CONFIG_MEMORY_SIZE.
> >
> > My understanding is that if you load a zImage at the correct
> > start address (0x60000000 IIRC) and then execute it using bootz
> > then the kernel should relocate and run from that address.
>
> Hmm...
> This means 3) is not needed, but it didn't work without 3)
> Is it R8A7778 or Bock-W DT code issue ?
Now, Bock-W start works with attached patch
Is it correct for you ?
I used simon/topic/defconfig-consolidation+next-20130403
(I guess there is no tag for it ?)
-- for bock-w ---------------------------
diff --git a/arch/arm/boot/dts/r8a7778-bockw.dts b/arch/arm/boot/dts/r8a7778-bockw.dts
index 0076b1e..1242940 100644
--- a/arch/arm/boot/dts/r8a7778-bockw.dts
+++ b/arch/arm/boot/dts/r8a7778-bockw.dts
@@ -27,6 +27,6 @@
memory {
device_type = "memory";
- reg = <0x60000000 0x10000000>;
+ reg = <0x40000000 0x10000000>;
};
};
diff --git a/arch/arm/configs/shmobile_defconfig b/arch/arm/configs/shmobile_defconfig
index 7dba53f..c4b9940 100644
--- a/arch/arm/configs/shmobile_defconfig
+++ b/arch/arm/configs/shmobile_defconfig
@@ -14,10 +14,12 @@ CONFIG_SLAB=y
CONFIG_ARCH_SHMOBILE=y
CONFIG_ARCH_SH7372=y
CONFIG_ARCH_R8A7740=y
+CONFIG_ARCH_R8A7778=y
CONFIG_ARCH_R8A7790=y
CONFIG_ARCH_EMEV2=y
CONFIG_MACH_MACKEREL=y
CONFIG_MACH_ARMADILLO800EVA=y
+CONFIG_MACH_BOCKW=y
CONFIG_MACH_LAGER=y
CONFIG_MACH_KZM9D=y
# CONFIG_SH_TIMER_TMU is not set
Best regards
---
Kuninori Morimoto
^ permalink raw reply related [flat|nested] 38+ messages in thread
* [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation
@ 2013-04-08 3:16 ` Kuninori Morimoto
0 siblings, 0 replies; 38+ messages in thread
From: Kuninori Morimoto @ 2013-04-08 3:16 UTC (permalink / raw)
To: linux-arm-kernel
Hi Simon
> > Unfortunately not, the idea is not to modify CONFIG_MEMORY_START
> > or CONFIG_MEMORY_SIZE.
> >
> > My understanding is that if you load a zImage at the correct
> > start address (0x60000000 IIRC) and then execute it using bootz
> > then the kernel should relocate and run from that address.
>
> Hmm...
> This means 3) is not needed, but it didn't work without 3)
> Is it R8A7778 or Bock-W DT code issue ?
Now, Bock-W start works with attached patch
Is it correct for you ?
I used simon/topic/defconfig-consolidation+next-20130403
(I guess there is no tag for it ?)
-- for bock-w ---------------------------
diff --git a/arch/arm/boot/dts/r8a7778-bockw.dts b/arch/arm/boot/dts/r8a7778-bockw.dts
index 0076b1e..1242940 100644
--- a/arch/arm/boot/dts/r8a7778-bockw.dts
+++ b/arch/arm/boot/dts/r8a7778-bockw.dts
@@ -27,6 +27,6 @@
memory {
device_type = "memory";
- reg = <0x60000000 0x10000000>;
+ reg = <0x40000000 0x10000000>;
};
};
diff --git a/arch/arm/configs/shmobile_defconfig b/arch/arm/configs/shmobile_defconfig
index 7dba53f..c4b9940 100644
--- a/arch/arm/configs/shmobile_defconfig
+++ b/arch/arm/configs/shmobile_defconfig
@@ -14,10 +14,12 @@ CONFIG_SLAB=y
CONFIG_ARCH_SHMOBILE=y
CONFIG_ARCH_SH7372=y
CONFIG_ARCH_R8A7740=y
+CONFIG_ARCH_R8A7778=y
CONFIG_ARCH_R8A7790=y
CONFIG_ARCH_EMEV2=y
CONFIG_MACH_MACKEREL=y
CONFIG_MACH_ARMADILLO800EVA=y
+CONFIG_MACH_BOCKW=y
CONFIG_MACH_LAGER=y
CONFIG_MACH_KZM9D=y
# CONFIG_SH_TIMER_TMU is not set
Best regards
---
Kuninori Morimoto
^ permalink raw reply related [flat|nested] 38+ messages in thread
end of thread, other threads:[~2013-04-08 3:16 UTC | newest]
Thread overview: 38+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-04-04 3:29 [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation Simon Horman
2013-04-04 3:29 ` Simon Horman
2013-04-04 3:29 ` [RFC/PATCH 1/7] ARM: shmobile: prune defconfig Simon Horman
2013-04-04 3:29 ` Simon Horman
2013-04-04 3:29 ` [RFC/PATCH 2/7] ARM: shmobile: make defconfig canonical Simon Horman
2013-04-04 3:29 ` Simon Horman
2013-04-04 3:29 ` [RFC/PATCH 3/7] ARM: shmobile: Add kzm9d to consolidated defconfig Simon Horman
2013-04-04 3:29 ` Simon Horman
2013-04-04 3:29 ` [RFC/PATCH 4/7] ARM: shmobile: Add mackerel " Simon Horman
2013-04-04 3:29 ` Simon Horman
2013-04-04 3:29 ` [RFC/PATCH 5/7] ARM: shmobile: defconfig: Remove armadillo800eva defconfig Simon Horman
2013-04-04 3:29 ` Simon Horman
2013-04-04 3:29 ` [RFC/PATCH 6/7] ARM: shmobile: defconfig: Remove kzm9d defconfig Simon Horman
2013-04-04 3:29 ` Simon Horman
2013-04-04 3:29 ` [RFC/PATCH 7/7] ARM: shmobile: defconfig: Remove mackerel defconfig Simon Horman
2013-04-04 3:29 ` Simon Horman
2013-04-04 7:46 ` [RFC/PATCH 8/7] ARCH: shmobile: defconfig consolidation (repost) Simon Horman
2013-04-04 7:46 ` Simon Horman
2013-04-04 11:20 ` [RFC/PATCH 0/7] ARCH: shmobile: defconfig consolidation Laurent Pinchart
2013-04-04 11:20 ` Laurent Pinchart
2013-04-05 0:30 ` Simon Horman
2013-04-05 0:30 ` Simon Horman
2013-04-05 0:37 ` Laurent Pinchart
2013-04-05 0:37 ` Laurent Pinchart
2013-04-05 0:49 ` Simon Horman
2013-04-05 0:49 ` Simon Horman
2013-04-05 10:07 ` Laurent Pinchart
2013-04-05 10:07 ` Laurent Pinchart
2013-04-05 3:08 ` Simon Horman
2013-04-05 3:08 ` Simon Horman
2013-04-08 1:07 ` Kuninori Morimoto
2013-04-08 1:07 ` Kuninori Morimoto
2013-04-08 2:16 ` Simon Horman
2013-04-08 2:16 ` Simon Horman
2013-04-08 2:52 ` Kuninori Morimoto
2013-04-08 2:52 ` Kuninori Morimoto
2013-04-08 3:16 ` Kuninori Morimoto
2013-04-08 3:16 ` Kuninori Morimoto
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.