* [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig
@ 2019-02-20 7:45 ` Sugaya Taichi
0 siblings, 0 replies; 16+ messages in thread
From: Sugaya Taichi @ 2019-02-20 7:45 UTC (permalink / raw)
To: linux-kernel, linux-arm-kernel, soc
Cc: Arnd Bergmann, Takao Orito, Kazuhiro Kasai, Shinji Kanematsu,
Jassi Brar, Masami Hiramatsu, Sugaya Taichi
This patch adds the minimal defconfig for the Milbeaut M10V.
Signed-off-by: Sugaya Taichi <sugaya.taichi@socionext.com>
---
arch/arm/configs/milbeaut_m10v_defconfig | 175 +++++++++++++++++++++++++++++++
arch/arm/configs/multi_v7_defconfig | 2 +
2 files changed, 177 insertions(+)
create mode 100644 arch/arm/configs/milbeaut_m10v_defconfig
diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig
new file mode 100644
index 0000000..a263211
--- /dev/null
+++ b/arch/arm/configs/milbeaut_m10v_defconfig
@@ -0,0 +1,175 @@
+# CONFIG_LOCALVERSION_AUTO is not set
+CONFIG_DEBUG_SEMIHOSTING=y
+CONFIG_DEFAULT_HOSTNAME="mlbel"
+CONFIG_SYSVIPC=y
+CONFIG_POSIX_MQUEUE=y
+CONFIG_FHANDLE=y
+CONFIG_NO_HZ_FULL=y
+CONFIG_NO_HZ_FULL_ALL=y
+CONFIG_NO_HZ_FULL_SYSIDLE=y
+CONFIG_NO_HZ_FULL_SYSIDLE_SMALL=4
+CONFIG_HIGH_RES_TIMERS=y
+CONFIG_BSD_PROCESS_ACCT=y
+CONFIG_BSD_PROCESS_ACCT_V3=y
+CONFIG_TASKSTATS=y
+CONFIG_TASK_DELAY_ACCT=y
+CONFIG_TASK_XACCT=y
+CONFIG_TASK_IO_ACCOUNTING=y
+CONFIG_IKCONFIG=y
+CONFIG_IKCONFIG_PROC=y
+CONFIG_CGROUPS=y
+CONFIG_CGROUP_DEBUG=y
+CONFIG_CPUSETS=y
+CONFIG_CGROUP_SCHED=y
+CONFIG_CFS_BANDWIDTH=y
+CONFIG_RT_GROUP_SCHED=y
+CONFIG_NAMESPACES=y
+CONFIG_USER_NS=y
+CONFIG_BLK_DEV_INITRD=y
+CONFIG_CC_OPTIMIZE_FOR_SIZE=y
+CONFIG_KALLSYMS_ALL=y
+# CONFIG_COMPAT_BRK is not set
+CONFIG_SLAB=y
+CONFIG_PROFILING=y
+# CONFIG_OPROFILE=m
+CONFIG_MODULES=y
+CONFIG_MODULE_UNLOAD=y
+CONFIG_ARCH_MILBEAUT=y
+CONFIG_ARCH_MILBEAUT_M10V=y
+# CONFIG_CACHE_L2X0 is not set
+CONFIG_ARM_ERRATA_754322=y
+CONFIG_ARM_ERRATA_775420=y
+CONFIG_SMP=y
+# CONFIG_ARM_CPU_TOPOLOGY is not set
+CONFIG_HAVE_ARM_ARCH_TIMER=y
+CONFIG_PREEMPT=y
+CONFIG_THUMB2_KERNEL=y
+CONFIG_HIGHMEM=y
+# CONFIG_COMPACTION is not set
+CONFIG_CMA=y
+# CONFIG_ATAGS is not set
+CONFIG_ZBOOT_ROM_TEXT=0x0
+CONFIG_ZBOOT_ROM_BSS=0x0
+CONFIG_KEXEC=y
+CONFIG_CPU_FREQ=y
+CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
+CONFIG_CPUFREQ_DT=y
+CONFIG_CPU_IDLE=y
+CONFIG_VFP=y
+CONFIG_NEON=y
+CONFIG_KERNEL_MODE_NEON=y
+CONFIG_WQ_POWER_EFFICIENT_DEFAULT=y
+CONFIG_UNIX=y
+CONFIG_DEVTMPFS=y
+CONFIG_DEVTMPFS_MOUNT=y
+CONFIG_DMA_CMA=y
+CONFIG_CMA_SIZE_MBYTES=16
+CONFIG_BLK_DEV_LOOP=y
+CONFIG_BLK_DEV_LOOP_MIN_COUNT=2
+CONFIG_BLK_DEV_RAM=y
+CONFIG_SCSI=y
+CONFIG_BLK_DEV_SD=y
+CONFIG_VETH=y
+CONFIG_INPUT_POLLDEV=y
+# CONFIG_INPUT_MOUSEDEV is not set
+CONFIG_INPUT_EVDEV=y
+# CONFIG_INPUT_KEYBOARD is not set
+# CONFIG_INPUT_MOUSE is not set
+CONFIG_SERIO_LIBPS2=y
+CONFIG_LEGACY_PTY_COUNT=4
+CONFIG_GPIOLIB=y
+CONFIG_GPIO_SYSFS=y
+# CONFIG_HWMON is not set
+CONFIG_WATCHDOG=y
+CONFIG_SOFT_WATCHDOG=m
+CONFIG_REGULATOR=y
+CONFIG_REGULATOR_DEBUG=y
+CONFIG_REGULATOR_S6AP412=y
+CONFIG_MEDIA_SUPPORT=y
+CONFIG_MEDIA_CAMERA_SUPPORT=y
+CONFIG_MEDIA_CONTROLLER=y
+CONFIG_VIDEO_ADV_DEBUG=y
+CONFIG_SOC_CAMERA=y
+CONFIG_SOC_CAMERA_PLATFORM=y
+# CONFIG_VGA_ARB is not set
+CONFIG_DMADEVICES=y
+CONFIG_UIO=y
+# CONFIG_IOMMU_SUPPORT is not set
+CONFIG_RESET_CONTROLLER=y
+CONFIG_EXT4_FS=y
+# CONFIG_EXT4_USE_FOR_EXT23 is not set
+# CONFIG_XFS_FS is not set
+CONFIG_FANOTIFY=y
+CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y
+CONFIG_QUOTA=y
+CONFIG_AUTOFS4_FS=y
+# CONFIG_FUSE_FS is not set
+CONFIG_FSCACHE=y
+CONFIG_FSCACHE_STATS=y
+CONFIG_FSCACHE_HISTOGRAM=y
+CONFIG_MSDOS_FS=y
+CONFIG_VFAT_FS=y
+CONFIG_FAT_DEFAULT_CODEPAGE=932
+CONFIG_TMPFS=y
+CONFIG_TMPFS_POSIX_ACL=y
+CONFIG_ROMFS_FS=y
+CONFIG_ROMFS_BACKED_BY_BOTH=y
+CONFIG_NFS_FS=m
+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_CODEPAGE_936=y
+CONFIG_NLS_CODEPAGE_950=y
+CONFIG_NLS_CODEPAGE_932=y
+CONFIG_NLS_CODEPAGE_949=y
+CONFIG_NLS_CODEPAGE_874=y
+CONFIG_NLS_ISO8859_8=y
+CONFIG_NLS_CODEPAGE_1250=y
+CONFIG_NLS_CODEPAGE_1251=y
+CONFIG_NLS_ASCII=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_MAC_ROMAN=y
+CONFIG_NLS_MAC_CELTIC=y
+CONFIG_NLS_MAC_CENTEURO=y
+CONFIG_NLS_MAC_CROATIAN=y
+CONFIG_NLS_MAC_CYRILLIC=y
+CONFIG_NLS_MAC_GAELIC=y
+CONFIG_NLS_MAC_GREEK=y
+CONFIG_NLS_MAC_ICELAND=y
+CONFIG_NLS_MAC_INUIT=y
+CONFIG_NLS_MAC_ROMANIAN=y
+CONFIG_NLS_MAC_TURKISH=y
+CONFIG_NLS_UTF8=y
+CONFIG_PRINTK_TIME=y
+CONFIG_HEADERS_CHECK=y
+CONFIG_RCU_TORTURE_TEST=m
+CONFIG_RCU_CPU_STALL_TIMEOUT=60
+CONFIG_KGDB=y
+CONFIG_KEYS=y
+CONFIG_ENCRYPTED_KEYS=y
+CONFIG_SECURITY=y
+CONFIG_FONTS=y
diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
index 5bee34a..6753805 100644
--- a/arch/arm/configs/multi_v7_defconfig
+++ b/arch/arm/configs/multi_v7_defconfig
@@ -54,6 +54,8 @@ CONFIG_SOC_VF610=y
CONFIG_ARCH_KEYSTONE=y
CONFIG_ARCH_MEDIATEK=y
CONFIG_ARCH_MESON=y
+CONFIG_ARCH_MILBEAUT=y
+CONFIG_ARCH_MILBEAUT_M10V=y
CONFIG_ARCH_MVEBU=y
CONFIG_MACH_ARMADA_370=y
CONFIG_MACH_ARMADA_375=y
--
1.9.1
^ permalink raw reply related [flat|nested] 16+ messages in thread
* [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig
@ 2019-02-20 7:45 ` Sugaya Taichi
0 siblings, 0 replies; 16+ messages in thread
From: Sugaya Taichi @ 2019-02-20 7:45 UTC (permalink / raw)
To: linux-kernel, linux-arm-kernel, soc
Cc: Shinji Kanematsu, Arnd Bergmann, Masami Hiramatsu, Sugaya Taichi,
Jassi Brar, Takao Orito, Kazuhiro Kasai
This patch adds the minimal defconfig for the Milbeaut M10V.
Signed-off-by: Sugaya Taichi <sugaya.taichi@socionext.com>
---
arch/arm/configs/milbeaut_m10v_defconfig | 175 +++++++++++++++++++++++++++++++
arch/arm/configs/multi_v7_defconfig | 2 +
2 files changed, 177 insertions(+)
create mode 100644 arch/arm/configs/milbeaut_m10v_defconfig
diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig
new file mode 100644
index 0000000..a263211
--- /dev/null
+++ b/arch/arm/configs/milbeaut_m10v_defconfig
@@ -0,0 +1,175 @@
+# CONFIG_LOCALVERSION_AUTO is not set
+CONFIG_DEBUG_SEMIHOSTING=y
+CONFIG_DEFAULT_HOSTNAME="mlbel"
+CONFIG_SYSVIPC=y
+CONFIG_POSIX_MQUEUE=y
+CONFIG_FHANDLE=y
+CONFIG_NO_HZ_FULL=y
+CONFIG_NO_HZ_FULL_ALL=y
+CONFIG_NO_HZ_FULL_SYSIDLE=y
+CONFIG_NO_HZ_FULL_SYSIDLE_SMALL=4
+CONFIG_HIGH_RES_TIMERS=y
+CONFIG_BSD_PROCESS_ACCT=y
+CONFIG_BSD_PROCESS_ACCT_V3=y
+CONFIG_TASKSTATS=y
+CONFIG_TASK_DELAY_ACCT=y
+CONFIG_TASK_XACCT=y
+CONFIG_TASK_IO_ACCOUNTING=y
+CONFIG_IKCONFIG=y
+CONFIG_IKCONFIG_PROC=y
+CONFIG_CGROUPS=y
+CONFIG_CGROUP_DEBUG=y
+CONFIG_CPUSETS=y
+CONFIG_CGROUP_SCHED=y
+CONFIG_CFS_BANDWIDTH=y
+CONFIG_RT_GROUP_SCHED=y
+CONFIG_NAMESPACES=y
+CONFIG_USER_NS=y
+CONFIG_BLK_DEV_INITRD=y
+CONFIG_CC_OPTIMIZE_FOR_SIZE=y
+CONFIG_KALLSYMS_ALL=y
+# CONFIG_COMPAT_BRK is not set
+CONFIG_SLAB=y
+CONFIG_PROFILING=y
+# CONFIG_OPROFILE=m
+CONFIG_MODULES=y
+CONFIG_MODULE_UNLOAD=y
+CONFIG_ARCH_MILBEAUT=y
+CONFIG_ARCH_MILBEAUT_M10V=y
+# CONFIG_CACHE_L2X0 is not set
+CONFIG_ARM_ERRATA_754322=y
+CONFIG_ARM_ERRATA_775420=y
+CONFIG_SMP=y
+# CONFIG_ARM_CPU_TOPOLOGY is not set
+CONFIG_HAVE_ARM_ARCH_TIMER=y
+CONFIG_PREEMPT=y
+CONFIG_THUMB2_KERNEL=y
+CONFIG_HIGHMEM=y
+# CONFIG_COMPACTION is not set
+CONFIG_CMA=y
+# CONFIG_ATAGS is not set
+CONFIG_ZBOOT_ROM_TEXT=0x0
+CONFIG_ZBOOT_ROM_BSS=0x0
+CONFIG_KEXEC=y
+CONFIG_CPU_FREQ=y
+CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND=y
+CONFIG_CPUFREQ_DT=y
+CONFIG_CPU_IDLE=y
+CONFIG_VFP=y
+CONFIG_NEON=y
+CONFIG_KERNEL_MODE_NEON=y
+CONFIG_WQ_POWER_EFFICIENT_DEFAULT=y
+CONFIG_UNIX=y
+CONFIG_DEVTMPFS=y
+CONFIG_DEVTMPFS_MOUNT=y
+CONFIG_DMA_CMA=y
+CONFIG_CMA_SIZE_MBYTES=16
+CONFIG_BLK_DEV_LOOP=y
+CONFIG_BLK_DEV_LOOP_MIN_COUNT=2
+CONFIG_BLK_DEV_RAM=y
+CONFIG_SCSI=y
+CONFIG_BLK_DEV_SD=y
+CONFIG_VETH=y
+CONFIG_INPUT_POLLDEV=y
+# CONFIG_INPUT_MOUSEDEV is not set
+CONFIG_INPUT_EVDEV=y
+# CONFIG_INPUT_KEYBOARD is not set
+# CONFIG_INPUT_MOUSE is not set
+CONFIG_SERIO_LIBPS2=y
+CONFIG_LEGACY_PTY_COUNT=4
+CONFIG_GPIOLIB=y
+CONFIG_GPIO_SYSFS=y
+# CONFIG_HWMON is not set
+CONFIG_WATCHDOG=y
+CONFIG_SOFT_WATCHDOG=m
+CONFIG_REGULATOR=y
+CONFIG_REGULATOR_DEBUG=y
+CONFIG_REGULATOR_S6AP412=y
+CONFIG_MEDIA_SUPPORT=y
+CONFIG_MEDIA_CAMERA_SUPPORT=y
+CONFIG_MEDIA_CONTROLLER=y
+CONFIG_VIDEO_ADV_DEBUG=y
+CONFIG_SOC_CAMERA=y
+CONFIG_SOC_CAMERA_PLATFORM=y
+# CONFIG_VGA_ARB is not set
+CONFIG_DMADEVICES=y
+CONFIG_UIO=y
+# CONFIG_IOMMU_SUPPORT is not set
+CONFIG_RESET_CONTROLLER=y
+CONFIG_EXT4_FS=y
+# CONFIG_EXT4_USE_FOR_EXT23 is not set
+# CONFIG_XFS_FS is not set
+CONFIG_FANOTIFY=y
+CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y
+CONFIG_QUOTA=y
+CONFIG_AUTOFS4_FS=y
+# CONFIG_FUSE_FS is not set
+CONFIG_FSCACHE=y
+CONFIG_FSCACHE_STATS=y
+CONFIG_FSCACHE_HISTOGRAM=y
+CONFIG_MSDOS_FS=y
+CONFIG_VFAT_FS=y
+CONFIG_FAT_DEFAULT_CODEPAGE=932
+CONFIG_TMPFS=y
+CONFIG_TMPFS_POSIX_ACL=y
+CONFIG_ROMFS_FS=y
+CONFIG_ROMFS_BACKED_BY_BOTH=y
+CONFIG_NFS_FS=m
+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_CODEPAGE_936=y
+CONFIG_NLS_CODEPAGE_950=y
+CONFIG_NLS_CODEPAGE_932=y
+CONFIG_NLS_CODEPAGE_949=y
+CONFIG_NLS_CODEPAGE_874=y
+CONFIG_NLS_ISO8859_8=y
+CONFIG_NLS_CODEPAGE_1250=y
+CONFIG_NLS_CODEPAGE_1251=y
+CONFIG_NLS_ASCII=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_MAC_ROMAN=y
+CONFIG_NLS_MAC_CELTIC=y
+CONFIG_NLS_MAC_CENTEURO=y
+CONFIG_NLS_MAC_CROATIAN=y
+CONFIG_NLS_MAC_CYRILLIC=y
+CONFIG_NLS_MAC_GAELIC=y
+CONFIG_NLS_MAC_GREEK=y
+CONFIG_NLS_MAC_ICELAND=y
+CONFIG_NLS_MAC_INUIT=y
+CONFIG_NLS_MAC_ROMANIAN=y
+CONFIG_NLS_MAC_TURKISH=y
+CONFIG_NLS_UTF8=y
+CONFIG_PRINTK_TIME=y
+CONFIG_HEADERS_CHECK=y
+CONFIG_RCU_TORTURE_TEST=m
+CONFIG_RCU_CPU_STALL_TIMEOUT=60
+CONFIG_KGDB=y
+CONFIG_KEYS=y
+CONFIG_ENCRYPTED_KEYS=y
+CONFIG_SECURITY=y
+CONFIG_FONTS=y
diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
index 5bee34a..6753805 100644
--- a/arch/arm/configs/multi_v7_defconfig
+++ b/arch/arm/configs/multi_v7_defconfig
@@ -54,6 +54,8 @@ CONFIG_SOC_VF610=y
CONFIG_ARCH_KEYSTONE=y
CONFIG_ARCH_MEDIATEK=y
CONFIG_ARCH_MESON=y
+CONFIG_ARCH_MILBEAUT=y
+CONFIG_ARCH_MILBEAUT_M10V=y
CONFIG_ARCH_MVEBU=y
CONFIG_MACH_ARMADA_370=y
CONFIG_MACH_ARMADA_375=y
--
1.9.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply related [flat|nested] 16+ messages in thread
* Re: [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig
2019-02-20 7:45 ` Sugaya Taichi
@ 2019-02-20 9:28 ` Arnd Bergmann
-1 siblings, 0 replies; 16+ messages in thread
From: Arnd Bergmann @ 2019-02-20 9:28 UTC (permalink / raw)
To: Sugaya Taichi
Cc: Linux Kernel Mailing List, Linux ARM, soc, Takao Orito,
Kazuhiro Kasai, Shinji Kanematsu, Jassi Brar, Masami Hiramatsu
On Wed, Feb 20, 2019 at 8:44 AM Sugaya Taichi
<sugaya.taichi@socionext.com> wrote:
> diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig
> new file mode 100644
> index 0000000..a263211
> --- /dev/null
> +++ b/arch/arm/configs/milbeaut_m10v_defconfig
> @@ -0,0 +1,175 @@
I no longer see anything here that should be turned off, but you
might want to run 'make savedefconfig' and use the output of that,
to make it easier to keep it up to date.
> diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
> index 5bee34a..6753805 100644
> --- a/arch/arm/configs/multi_v7_defconfig
> +++ b/arch/arm/configs/multi_v7_defconfig
> @@ -54,6 +54,8 @@ CONFIG_SOC_VF610=y
> CONFIG_ARCH_KEYSTONE=y
> CONFIG_ARCH_MEDIATEK=y
> CONFIG_ARCH_MESON=y
> +CONFIG_ARCH_MILBEAUT=y
> +CONFIG_ARCH_MILBEAUT_M10V=y
> CONFIG_ARCH_MVEBU=y
> CONFIG_MACH_ARMADA_370=y
> CONFIG_MACH_ARMADA_375=y
I'm surprised that you don't need to enable any drivers. Does this actually
boot on your hardware?
Arnd
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig
@ 2019-02-20 9:28 ` Arnd Bergmann
0 siblings, 0 replies; 16+ messages in thread
From: Arnd Bergmann @ 2019-02-20 9:28 UTC (permalink / raw)
To: Sugaya Taichi
Cc: Shinji Kanematsu, Masami Hiramatsu, Linux Kernel Mailing List,
Jassi Brar, soc, Takao Orito, Kazuhiro Kasai, Linux ARM
On Wed, Feb 20, 2019 at 8:44 AM Sugaya Taichi
<sugaya.taichi@socionext.com> wrote:
> diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig
> new file mode 100644
> index 0000000..a263211
> --- /dev/null
> +++ b/arch/arm/configs/milbeaut_m10v_defconfig
> @@ -0,0 +1,175 @@
I no longer see anything here that should be turned off, but you
might want to run 'make savedefconfig' and use the output of that,
to make it easier to keep it up to date.
> diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
> index 5bee34a..6753805 100644
> --- a/arch/arm/configs/multi_v7_defconfig
> +++ b/arch/arm/configs/multi_v7_defconfig
> @@ -54,6 +54,8 @@ CONFIG_SOC_VF610=y
> CONFIG_ARCH_KEYSTONE=y
> CONFIG_ARCH_MEDIATEK=y
> CONFIG_ARCH_MESON=y
> +CONFIG_ARCH_MILBEAUT=y
> +CONFIG_ARCH_MILBEAUT_M10V=y
> CONFIG_ARCH_MVEBU=y
> CONFIG_MACH_ARMADA_370=y
> CONFIG_MACH_ARMADA_375=y
I'm surprised that you don't need to enable any drivers. Does this actually
boot on your hardware?
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig
2019-02-20 9:28 ` Arnd Bergmann
@ 2019-02-20 11:27 ` Sugaya, Taichi
-1 siblings, 0 replies; 16+ messages in thread
From: Sugaya, Taichi @ 2019-02-20 11:27 UTC (permalink / raw)
To: Arnd Bergmann
Cc: Shinji Kanematsu, Masami Hiramatsu, Linux Kernel Mailing List,
Jassi Brar, soc, Takao Orito, Kazuhiro Kasai, Linux ARM
Hi
On 2019/02/20 18:28, Arnd Bergmann wrote:
> On Wed, Feb 20, 2019 at 8:44 AM Sugaya Taichi
> <sugaya.taichi@socionext.com> wrote:
>
>> diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig
>> new file mode 100644
>> index 0000000..a263211
>> --- /dev/null
>> +++ b/arch/arm/configs/milbeaut_m10v_defconfig
>> @@ -0,0 +1,175 @@
>
> I no longer see anything here that should be turned off, but you
> might want to run 'make savedefconfig' and use the output of that,
> to make it easier to keep it up to date.
>
I got it, I use the output of 'make savedefconfig'.
One question, is that OK to add some options on it?
-Because "CONFIG_ARCH_MILBEAUT" was not listed.
>> diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
>> index 5bee34a..6753805 100644
>> --- a/arch/arm/configs/multi_v7_defconfig
>> +++ b/arch/arm/configs/multi_v7_defconfig
>> @@ -54,6 +54,8 @@ CONFIG_SOC_VF610=y
>> CONFIG_ARCH_KEYSTONE=y
>> CONFIG_ARCH_MEDIATEK=y
>> CONFIG_ARCH_MESON=y
>> +CONFIG_ARCH_MILBEAUT=y
>> +CONFIG_ARCH_MILBEAUT_M10V=y
>> CONFIG_ARCH_MVEBU=y
>> CONFIG_MACH_ARMADA_370=y
>> CONFIG_MACH_ARMADA_375=y
>
> I'm surprised that you don't need to enable any drivers. Does this actually
> boot on your hardware?
>
Yes, but not exactly.
The series has not serial driver, so I add the driver temporarily and
confirm the boot log through earlycon.
The timer driver is selected by "CONFIG_ARCH_MILBEAUT_M10V", no need to
add the the"CONFIG_MILBEAUT_TIMER".
Here one more question.
Is this OK to submit a core support patch without any serial drivers?
Thanks,
Sugaya Taichi
> Arnd
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig
@ 2019-02-20 11:27 ` Sugaya, Taichi
0 siblings, 0 replies; 16+ messages in thread
From: Sugaya, Taichi @ 2019-02-20 11:27 UTC (permalink / raw)
To: Arnd Bergmann
Cc: Shinji Kanematsu, Masami Hiramatsu, Linux Kernel Mailing List,
Jassi Brar, soc, Takao Orito, Kazuhiro Kasai, Linux ARM
Hi
On 2019/02/20 18:28, Arnd Bergmann wrote:
> On Wed, Feb 20, 2019 at 8:44 AM Sugaya Taichi
> <sugaya.taichi@socionext.com> wrote:
>
>> diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig
>> new file mode 100644
>> index 0000000..a263211
>> --- /dev/null
>> +++ b/arch/arm/configs/milbeaut_m10v_defconfig
>> @@ -0,0 +1,175 @@
>
> I no longer see anything here that should be turned off, but you
> might want to run 'make savedefconfig' and use the output of that,
> to make it easier to keep it up to date.
>
I got it, I use the output of 'make savedefconfig'.
One question, is that OK to add some options on it?
-Because "CONFIG_ARCH_MILBEAUT" was not listed.
>> diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
>> index 5bee34a..6753805 100644
>> --- a/arch/arm/configs/multi_v7_defconfig
>> +++ b/arch/arm/configs/multi_v7_defconfig
>> @@ -54,6 +54,8 @@ CONFIG_SOC_VF610=y
>> CONFIG_ARCH_KEYSTONE=y
>> CONFIG_ARCH_MEDIATEK=y
>> CONFIG_ARCH_MESON=y
>> +CONFIG_ARCH_MILBEAUT=y
>> +CONFIG_ARCH_MILBEAUT_M10V=y
>> CONFIG_ARCH_MVEBU=y
>> CONFIG_MACH_ARMADA_370=y
>> CONFIG_MACH_ARMADA_375=y
>
> I'm surprised that you don't need to enable any drivers. Does this actually
> boot on your hardware?
>
Yes, but not exactly.
The series has not serial driver, so I add the driver temporarily and
confirm the boot log through earlycon.
The timer driver is selected by "CONFIG_ARCH_MILBEAUT_M10V", no need to
add the the"CONFIG_MILBEAUT_TIMER".
Here one more question.
Is this OK to submit a core support patch without any serial drivers?
Thanks,
Sugaya Taichi
> Arnd
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig
2019-02-20 11:27 ` Sugaya, Taichi
@ 2019-02-20 12:27 ` Arnd Bergmann
-1 siblings, 0 replies; 16+ messages in thread
From: Arnd Bergmann @ 2019-02-20 12:27 UTC (permalink / raw)
To: Sugaya, Taichi
Cc: Shinji Kanematsu, Masami Hiramatsu, Linux Kernel Mailing List,
Jassi Brar, soc, Takao Orito, Kazuhiro Kasai, Linux ARM
On Wed, Feb 20, 2019 at 12:27 PM Sugaya, Taichi
<sugaya.taichi@socionext.com> wrote:
>
> Hi
>
> On 2019/02/20 18:28, Arnd Bergmann wrote:
> > On Wed, Feb 20, 2019 at 8:44 AM Sugaya Taichi
> > <sugaya.taichi@socionext.com> wrote:
> >
> >> diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig
> >> new file mode 100644
> >> index 0000000..a263211
> >> --- /dev/null
> >> +++ b/arch/arm/configs/milbeaut_m10v_defconfig
> >> @@ -0,0 +1,175 @@
> >
> > I no longer see anything here that should be turned off, but you
> > might want to run 'make savedefconfig' and use the output of that,
> > to make it easier to keep it up to date.
> >
>
> I got it, I use the output of 'make savedefconfig'.
> One question, is that OK to add some options on it?
> -Because "CONFIG_ARCH_MILBEAUT" was not listed.
What I'd do here is to apply all the patches you want to get merged in
the next few releases before running 'savedefconfig' and use the output
of that.
If you already know that you will need the options, including
them now means you don't have to update the defconfig file
as much in the future.
> >> diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
> >> index 5bee34a..6753805 100644
> >> --- a/arch/arm/configs/multi_v7_defconfig
> >> +++ b/arch/arm/configs/multi_v7_defconfig
> >> @@ -54,6 +54,8 @@ CONFIG_SOC_VF610=y
> >> CONFIG_ARCH_KEYSTONE=y
> >> CONFIG_ARCH_MEDIATEK=y
> >> CONFIG_ARCH_MESON=y
> >> +CONFIG_ARCH_MILBEAUT=y
> >> +CONFIG_ARCH_MILBEAUT_M10V=y
> >> CONFIG_ARCH_MVEBU=y
> >> CONFIG_MACH_ARMADA_370=y
> >> CONFIG_MACH_ARMADA_375=y
> >
> > I'm surprised that you don't need to enable any drivers. Does this actually
> > boot on your hardware?
> >
>
> Yes, but not exactly.
> The series has not serial driver, so I add the driver temporarily and
> confirm the boot log through earlycon.
> The timer driver is selected by "CONFIG_ARCH_MILBEAUT_M10V", no need to
> add the the"CONFIG_MILBEAUT_TIMER".
>
> Here one more question.
> Is this OK to submit a core support patch without any serial drivers?
Yes, we are fairly flexible here. Greg also mentioned in the past that he's
fine with having us merge the serial driver through the arm-soc tree after
it has been reviewed, to keep it together with the platform support, same
thing for the clk, pinctrl, clocksource and irqchip drivers.
However, once the platform support is merged, we prefer that you do
any other driver changes (including newly added drivers) through the
subsystem trees.
Arnd
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig
@ 2019-02-20 12:27 ` Arnd Bergmann
0 siblings, 0 replies; 16+ messages in thread
From: Arnd Bergmann @ 2019-02-20 12:27 UTC (permalink / raw)
To: Sugaya, Taichi
Cc: Shinji Kanematsu, Masami Hiramatsu, Linux Kernel Mailing List,
Jassi Brar, soc, Takao Orito, Kazuhiro Kasai, Linux ARM
On Wed, Feb 20, 2019 at 12:27 PM Sugaya, Taichi
<sugaya.taichi@socionext.com> wrote:
>
> Hi
>
> On 2019/02/20 18:28, Arnd Bergmann wrote:
> > On Wed, Feb 20, 2019 at 8:44 AM Sugaya Taichi
> > <sugaya.taichi@socionext.com> wrote:
> >
> >> diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig
> >> new file mode 100644
> >> index 0000000..a263211
> >> --- /dev/null
> >> +++ b/arch/arm/configs/milbeaut_m10v_defconfig
> >> @@ -0,0 +1,175 @@
> >
> > I no longer see anything here that should be turned off, but you
> > might want to run 'make savedefconfig' and use the output of that,
> > to make it easier to keep it up to date.
> >
>
> I got it, I use the output of 'make savedefconfig'.
> One question, is that OK to add some options on it?
> -Because "CONFIG_ARCH_MILBEAUT" was not listed.
What I'd do here is to apply all the patches you want to get merged in
the next few releases before running 'savedefconfig' and use the output
of that.
If you already know that you will need the options, including
them now means you don't have to update the defconfig file
as much in the future.
> >> diff --git a/arch/arm/configs/multi_v7_defconfig b/arch/arm/configs/multi_v7_defconfig
> >> index 5bee34a..6753805 100644
> >> --- a/arch/arm/configs/multi_v7_defconfig
> >> +++ b/arch/arm/configs/multi_v7_defconfig
> >> @@ -54,6 +54,8 @@ CONFIG_SOC_VF610=y
> >> CONFIG_ARCH_KEYSTONE=y
> >> CONFIG_ARCH_MEDIATEK=y
> >> CONFIG_ARCH_MESON=y
> >> +CONFIG_ARCH_MILBEAUT=y
> >> +CONFIG_ARCH_MILBEAUT_M10V=y
> >> CONFIG_ARCH_MVEBU=y
> >> CONFIG_MACH_ARMADA_370=y
> >> CONFIG_MACH_ARMADA_375=y
> >
> > I'm surprised that you don't need to enable any drivers. Does this actually
> > boot on your hardware?
> >
>
> Yes, but not exactly.
> The series has not serial driver, so I add the driver temporarily and
> confirm the boot log through earlycon.
> The timer driver is selected by "CONFIG_ARCH_MILBEAUT_M10V", no need to
> add the the"CONFIG_MILBEAUT_TIMER".
>
> Here one more question.
> Is this OK to submit a core support patch without any serial drivers?
Yes, we are fairly flexible here. Greg also mentioned in the past that he's
fine with having us merge the serial driver through the arm-soc tree after
it has been reviewed, to keep it together with the platform support, same
thing for the clk, pinctrl, clocksource and irqchip drivers.
However, once the platform support is merged, we prefer that you do
any other driver changes (including newly added drivers) through the
subsystem trees.
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig
2019-02-20 12:27 ` Arnd Bergmann
@ 2019-02-20 13:16 ` Masami Hiramatsu
-1 siblings, 0 replies; 16+ messages in thread
From: Masami Hiramatsu @ 2019-02-20 13:16 UTC (permalink / raw)
To: Arnd Bergmann
Cc: Sugaya, Taichi, Shinji Kanematsu, Linux Kernel Mailing List,
Jassi Brar, soc, Takao Orito, Kazuhiro Kasai, Linux ARM
Hi Arnd,
2019年2月20日(水) 21:28 Arnd Bergmann <arnd@arndb.de>:
>
> On Wed, Feb 20, 2019 at 12:27 PM Sugaya, Taichi
> <sugaya.taichi@socionext.com> wrote:
> >
> > Hi
> >
> > On 2019/02/20 18:28, Arnd Bergmann wrote:
> > > On Wed, Feb 20, 2019 at 8:44 AM Sugaya Taichi
> > > <sugaya.taichi@socionext.com> wrote:
> > >
> > >> diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig
> > >> new file mode 100644
> > >> index 0000000..a263211
> > >> --- /dev/null
> > >> +++ b/arch/arm/configs/milbeaut_m10v_defconfig
> > >> @@ -0,0 +1,175 @@
> > >
> > > I no longer see anything here that should be turned off, but you
> > > might want to run 'make savedefconfig' and use the output of that,
> > > to make it easier to keep it up to date.
> > >
> >
> > I got it, I use the output of 'make savedefconfig'.
> > One question, is that OK to add some options on it?
> > -Because "CONFIG_ARCH_MILBEAUT" was not listed.
>
> What I'd do here is to apply all the patches you want to get merged in
> the next few releases before running 'savedefconfig' and use the output
> of that.
Let me check. Would you mean that the defconfig will include all those
drivers configs, which will not appear at this moment?
> If you already know that you will need the options, including
> them now means you don't have to update the defconfig file
> as much in the future.
I just concern that if other subsystem maintainer comments
on the config name. Even in that case, can we just update the
defconfig with new name?
Thank you,
--
Masami Hiramatsu
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig
@ 2019-02-20 13:16 ` Masami Hiramatsu
0 siblings, 0 replies; 16+ messages in thread
From: Masami Hiramatsu @ 2019-02-20 13:16 UTC (permalink / raw)
To: Arnd Bergmann
Cc: Shinji Kanematsu, Sugaya, Taichi, Linux Kernel Mailing List,
Jassi Brar, soc, Takao Orito, Kazuhiro Kasai, Linux ARM
Hi Arnd,
2019年2月20日(水) 21:28 Arnd Bergmann <arnd@arndb.de>:
>
> On Wed, Feb 20, 2019 at 12:27 PM Sugaya, Taichi
> <sugaya.taichi@socionext.com> wrote:
> >
> > Hi
> >
> > On 2019/02/20 18:28, Arnd Bergmann wrote:
> > > On Wed, Feb 20, 2019 at 8:44 AM Sugaya Taichi
> > > <sugaya.taichi@socionext.com> wrote:
> > >
> > >> diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig
> > >> new file mode 100644
> > >> index 0000000..a263211
> > >> --- /dev/null
> > >> +++ b/arch/arm/configs/milbeaut_m10v_defconfig
> > >> @@ -0,0 +1,175 @@
> > >
> > > I no longer see anything here that should be turned off, but you
> > > might want to run 'make savedefconfig' and use the output of that,
> > > to make it easier to keep it up to date.
> > >
> >
> > I got it, I use the output of 'make savedefconfig'.
> > One question, is that OK to add some options on it?
> > -Because "CONFIG_ARCH_MILBEAUT" was not listed.
>
> What I'd do here is to apply all the patches you want to get merged in
> the next few releases before running 'savedefconfig' and use the output
> of that.
Let me check. Would you mean that the defconfig will include all those
drivers configs, which will not appear at this moment?
> If you already know that you will need the options, including
> them now means you don't have to update the defconfig file
> as much in the future.
I just concern that if other subsystem maintainer comments
on the config name. Even in that case, can we just update the
defconfig with new name?
Thank you,
--
Masami Hiramatsu
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig
2019-02-20 13:16 ` Masami Hiramatsu
@ 2019-02-20 13:18 ` Arnd Bergmann
-1 siblings, 0 replies; 16+ messages in thread
From: Arnd Bergmann @ 2019-02-20 13:18 UTC (permalink / raw)
To: Masami Hiramatsu
Cc: Sugaya, Taichi, Shinji Kanematsu, Linux Kernel Mailing List,
Jassi Brar, soc, Takao Orito, Kazuhiro Kasai, Linux ARM
On Wed, Feb 20, 2019 at 2:16 PM Masami Hiramatsu
<masami.hiramatsu@linaro.org> wrote:
> 2019年2月20日(水) 21:28 Arnd Bergmann <arnd@arndb.de>:
> > On Wed, Feb 20, 2019 at 12:27 PM Sugaya, Taichi
> > <sugaya.taichi@socionext.com> wrote:
> > > On 2019/02/20 18:28, Arnd Bergmann wrote:
> > > > On Wed, Feb 20, 2019 at 8:44 AM Sugaya Taichi
> > > > <sugaya.taichi@socionext.com> wrote:
> > > >
> > > >> diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig
> > > >> new file mode 100644
> > > >> index 0000000..a263211
> > > >> --- /dev/null
> > > >> +++ b/arch/arm/configs/milbeaut_m10v_defconfig
> > > >> @@ -0,0 +1,175 @@
> > > >
> > > > I no longer see anything here that should be turned off, but you
> > > > might want to run 'make savedefconfig' and use the output of that,
> > > > to make it easier to keep it up to date.
> > > >
> > >
> > > I got it, I use the output of 'make savedefconfig'.
> > > One question, is that OK to add some options on it?
> > > -Because "CONFIG_ARCH_MILBEAUT" was not listed.
> >
> > What I'd do here is to apply all the patches you want to get merged in
> > the next few releases before running 'savedefconfig' and use the output
> > of that.
>
> Let me check. Would you mean that the defconfig will include all those
> drivers configs, which will not appear at this moment?
Correct.
> > If you already know that you will need the options, including
> > them now means you don't have to update the defconfig file
> > as much in the future.
>
> I just concern that if other subsystem maintainer comments
> on the config name. Even in that case, can we just update the
> defconfig with new name?
Yes, that's easy enough.
Arnd
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig
@ 2019-02-20 13:18 ` Arnd Bergmann
0 siblings, 0 replies; 16+ messages in thread
From: Arnd Bergmann @ 2019-02-20 13:18 UTC (permalink / raw)
To: Masami Hiramatsu
Cc: Shinji Kanematsu, Sugaya, Taichi, Linux Kernel Mailing List,
Jassi Brar, soc, Takao Orito, Kazuhiro Kasai, Linux ARM
On Wed, Feb 20, 2019 at 2:16 PM Masami Hiramatsu
<masami.hiramatsu@linaro.org> wrote:
> 2019年2月20日(水) 21:28 Arnd Bergmann <arnd@arndb.de>:
> > On Wed, Feb 20, 2019 at 12:27 PM Sugaya, Taichi
> > <sugaya.taichi@socionext.com> wrote:
> > > On 2019/02/20 18:28, Arnd Bergmann wrote:
> > > > On Wed, Feb 20, 2019 at 8:44 AM Sugaya Taichi
> > > > <sugaya.taichi@socionext.com> wrote:
> > > >
> > > >> diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig
> > > >> new file mode 100644
> > > >> index 0000000..a263211
> > > >> --- /dev/null
> > > >> +++ b/arch/arm/configs/milbeaut_m10v_defconfig
> > > >> @@ -0,0 +1,175 @@
> > > >
> > > > I no longer see anything here that should be turned off, but you
> > > > might want to run 'make savedefconfig' and use the output of that,
> > > > to make it easier to keep it up to date.
> > > >
> > >
> > > I got it, I use the output of 'make savedefconfig'.
> > > One question, is that OK to add some options on it?
> > > -Because "CONFIG_ARCH_MILBEAUT" was not listed.
> >
> > What I'd do here is to apply all the patches you want to get merged in
> > the next few releases before running 'savedefconfig' and use the output
> > of that.
>
> Let me check. Would you mean that the defconfig will include all those
> drivers configs, which will not appear at this moment?
Correct.
> > If you already know that you will need the options, including
> > them now means you don't have to update the defconfig file
> > as much in the future.
>
> I just concern that if other subsystem maintainer comments
> on the config name. Even in that case, can we just update the
> defconfig with new name?
Yes, that's easy enough.
Arnd
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig
2019-02-20 13:18 ` Arnd Bergmann
@ 2019-02-20 13:23 ` Masami Hiramatsu
-1 siblings, 0 replies; 16+ messages in thread
From: Masami Hiramatsu @ 2019-02-20 13:23 UTC (permalink / raw)
To: Arnd Bergmann
Cc: Sugaya, Taichi, Shinji Kanematsu, Linux Kernel Mailing List,
Jassi Brar, soc, Takao Orito, Kazuhiro Kasai, Linux ARM
Hi Arnd,
2019年2月20日(水) 22:18 Arnd Bergmann <arnd@arndb.de>:
>
> On Wed, Feb 20, 2019 at 2:16 PM Masami Hiramatsu
> <masami.hiramatsu@linaro.org> wrote:
> > 2019年2月20日(水) 21:28 Arnd Bergmann <arnd@arndb.de>:
> > > On Wed, Feb 20, 2019 at 12:27 PM Sugaya, Taichi
> > > <sugaya.taichi@socionext.com> wrote:
> > > > On 2019/02/20 18:28, Arnd Bergmann wrote:
> > > > > On Wed, Feb 20, 2019 at 8:44 AM Sugaya Taichi
> > > > > <sugaya.taichi@socionext.com> wrote:
> > > > >
> > > > >> diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig
> > > > >> new file mode 100644
> > > > >> index 0000000..a263211
> > > > >> --- /dev/null
> > > > >> +++ b/arch/arm/configs/milbeaut_m10v_defconfig
> > > > >> @@ -0,0 +1,175 @@
> > > > >
> > > > > I no longer see anything here that should be turned off, but you
> > > > > might want to run 'make savedefconfig' and use the output of that,
> > > > > to make it easier to keep it up to date.
> > > > >
> > > >
> > > > I got it, I use the output of 'make savedefconfig'.
> > > > One question, is that OK to add some options on it?
> > > > -Because "CONFIG_ARCH_MILBEAUT" was not listed.
> > >
> > > What I'd do here is to apply all the patches you want to get merged in
> > > the next few releases before running 'savedefconfig' and use the output
> > > of that.
> >
> > Let me check. Would you mean that the defconfig will include all those
> > drivers configs, which will not appear at this moment?
>
> Correct.
>
> > > If you already know that you will need the options, including
> > > them now means you don't have to update the defconfig file
> > > as much in the future.
> >
> > I just concern that if other subsystem maintainer comments
> > on the config name. Even in that case, can we just update the
> > defconfig with new name?
>
> Yes, that's easy enough.
OK, I got it :)
Thank you!
>
> Arnd
--
Masami Hiramatsu
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig
@ 2019-02-20 13:23 ` Masami Hiramatsu
0 siblings, 0 replies; 16+ messages in thread
From: Masami Hiramatsu @ 2019-02-20 13:23 UTC (permalink / raw)
To: Arnd Bergmann
Cc: Shinji Kanematsu, Sugaya, Taichi, Linux Kernel Mailing List,
Jassi Brar, soc, Takao Orito, Kazuhiro Kasai, Linux ARM
Hi Arnd,
2019年2月20日(水) 22:18 Arnd Bergmann <arnd@arndb.de>:
>
> On Wed, Feb 20, 2019 at 2:16 PM Masami Hiramatsu
> <masami.hiramatsu@linaro.org> wrote:
> > 2019年2月20日(水) 21:28 Arnd Bergmann <arnd@arndb.de>:
> > > On Wed, Feb 20, 2019 at 12:27 PM Sugaya, Taichi
> > > <sugaya.taichi@socionext.com> wrote:
> > > > On 2019/02/20 18:28, Arnd Bergmann wrote:
> > > > > On Wed, Feb 20, 2019 at 8:44 AM Sugaya Taichi
> > > > > <sugaya.taichi@socionext.com> wrote:
> > > > >
> > > > >> diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig
> > > > >> new file mode 100644
> > > > >> index 0000000..a263211
> > > > >> --- /dev/null
> > > > >> +++ b/arch/arm/configs/milbeaut_m10v_defconfig
> > > > >> @@ -0,0 +1,175 @@
> > > > >
> > > > > I no longer see anything here that should be turned off, but you
> > > > > might want to run 'make savedefconfig' and use the output of that,
> > > > > to make it easier to keep it up to date.
> > > > >
> > > >
> > > > I got it, I use the output of 'make savedefconfig'.
> > > > One question, is that OK to add some options on it?
> > > > -Because "CONFIG_ARCH_MILBEAUT" was not listed.
> > >
> > > What I'd do here is to apply all the patches you want to get merged in
> > > the next few releases before running 'savedefconfig' and use the output
> > > of that.
> >
> > Let me check. Would you mean that the defconfig will include all those
> > drivers configs, which will not appear at this moment?
>
> Correct.
>
> > > If you already know that you will need the options, including
> > > them now means you don't have to update the defconfig file
> > > as much in the future.
> >
> > I just concern that if other subsystem maintainer comments
> > on the config name. Even in that case, can we just update the
> > defconfig with new name?
>
> Yes, that's easy enough.
OK, I got it :)
Thank you!
>
> Arnd
--
Masami Hiramatsu
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig
2019-02-20 13:23 ` Masami Hiramatsu
@ 2019-02-21 0:36 ` Sugaya, Taichi
-1 siblings, 0 replies; 16+ messages in thread
From: Sugaya, Taichi @ 2019-02-21 0:36 UTC (permalink / raw)
To: Masami Hiramatsu, Arnd Bergmann
Cc: Shinji Kanematsu, Linux Kernel Mailing List, Jassi Brar, soc,
Takao Orito, Kazuhiro Kasai, Linux ARM
Hi,
On 2019/02/20 22:23, Masami Hiramatsu wrote:
> Hi Arnd,
>
> 2019年2月20日(水) 22:18 Arnd Bergmann <arnd@arndb.de>:
>>
>> On Wed, Feb 20, 2019 at 2:16 PM Masami Hiramatsu
>> <masami.hiramatsu@linaro.org> wrote:
>>> 2019年2月20日(水) 21:28 Arnd Bergmann <arnd@arndb.de>:
>>>> On Wed, Feb 20, 2019 at 12:27 PM Sugaya, Taichi
>>>> <sugaya.taichi@socionext.com> wrote:
>>>>> On 2019/02/20 18:28, Arnd Bergmann wrote:
>>>>>> On Wed, Feb 20, 2019 at 8:44 AM Sugaya Taichi
>>>>>> <sugaya.taichi@socionext.com> wrote:
>>>>>>
>>>>>>> diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig
>>>>>>> new file mode 100644
>>>>>>> index 0000000..a263211
>>>>>>> --- /dev/null
>>>>>>> +++ b/arch/arm/configs/milbeaut_m10v_defconfig
>>>>>>> @@ -0,0 +1,175 @@
>>>>>>
>>>>>> I no longer see anything here that should be turned off, but you
>>>>>> might want to run 'make savedefconfig' and use the output of that,
>>>>>> to make it easier to keep it up to date.
>>>>>>
>>>>>
>>>>> I got it, I use the output of 'make savedefconfig'.
>>>>> One question, is that OK to add some options on it?
>>>>> -Because "CONFIG_ARCH_MILBEAUT" was not listed.
>>>>
>>>> What I'd do here is to apply all the patches you want to get merged in
>>>> the next few releases before running 'savedefconfig' and use the output
>>>> of that.
>>>
>>> Let me check. Would you mean that the defconfig will include all those
>>> drivers configs, which will not appear at this moment?
>>
>> Correct.
>>
>>>> If you already know that you will need the options, including
>>>> them now means you don't have to update the defconfig file
>>>> as much in the future.
>>>
>>> I just concern that if other subsystem maintainer comments
>>> on the config name. Even in that case, can we just update the
>>> defconfig with new name?
>>
>> Yes, that's easy enough.
>
> OK, I got it :)
>
> Thank you!
>
Thank you for the detail. I got it too.
>>
>> Arnd
>
>
>
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig
@ 2019-02-21 0:36 ` Sugaya, Taichi
0 siblings, 0 replies; 16+ messages in thread
From: Sugaya, Taichi @ 2019-02-21 0:36 UTC (permalink / raw)
To: Masami Hiramatsu, Arnd Bergmann
Cc: Shinji Kanematsu, Linux Kernel Mailing List, Jassi Brar, soc,
Takao Orito, Kazuhiro Kasai, Linux ARM
Hi,
On 2019/02/20 22:23, Masami Hiramatsu wrote:
> Hi Arnd,
>
> 2019年2月20日(水) 22:18 Arnd Bergmann <arnd@arndb.de>:
>>
>> On Wed, Feb 20, 2019 at 2:16 PM Masami Hiramatsu
>> <masami.hiramatsu@linaro.org> wrote:
>>> 2019年2月20日(水) 21:28 Arnd Bergmann <arnd@arndb.de>:
>>>> On Wed, Feb 20, 2019 at 12:27 PM Sugaya, Taichi
>>>> <sugaya.taichi@socionext.com> wrote:
>>>>> On 2019/02/20 18:28, Arnd Bergmann wrote:
>>>>>> On Wed, Feb 20, 2019 at 8:44 AM Sugaya Taichi
>>>>>> <sugaya.taichi@socionext.com> wrote:
>>>>>>
>>>>>>> diff --git a/arch/arm/configs/milbeaut_m10v_defconfig b/arch/arm/configs/milbeaut_m10v_defconfig
>>>>>>> new file mode 100644
>>>>>>> index 0000000..a263211
>>>>>>> --- /dev/null
>>>>>>> +++ b/arch/arm/configs/milbeaut_m10v_defconfig
>>>>>>> @@ -0,0 +1,175 @@
>>>>>>
>>>>>> I no longer see anything here that should be turned off, but you
>>>>>> might want to run 'make savedefconfig' and use the output of that,
>>>>>> to make it easier to keep it up to date.
>>>>>>
>>>>>
>>>>> I got it, I use the output of 'make savedefconfig'.
>>>>> One question, is that OK to add some options on it?
>>>>> -Because "CONFIG_ARCH_MILBEAUT" was not listed.
>>>>
>>>> What I'd do here is to apply all the patches you want to get merged in
>>>> the next few releases before running 'savedefconfig' and use the output
>>>> of that.
>>>
>>> Let me check. Would you mean that the defconfig will include all those
>>> drivers configs, which will not appear at this moment?
>>
>> Correct.
>>
>>>> If you already know that you will need the options, including
>>>> them now means you don't have to update the defconfig file
>>>> as much in the future.
>>>
>>> I just concern that if other subsystem maintainer comments
>>> on the config name. Even in that case, can we just update the
>>> defconfig with new name?
>>
>> Yes, that's easy enough.
>
> OK, I got it :)
>
> Thank you!
>
Thank you for the detail. I got it too.
>>
>> Arnd
>
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2019-02-21 0:36 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-02-20 7:45 [PATCH v3 9/9] ARM: configs: Add Milbeaut M10V defconfig Sugaya Taichi
2019-02-20 7:45 ` Sugaya Taichi
2019-02-20 9:28 ` Arnd Bergmann
2019-02-20 9:28 ` Arnd Bergmann
2019-02-20 11:27 ` Sugaya, Taichi
2019-02-20 11:27 ` Sugaya, Taichi
2019-02-20 12:27 ` Arnd Bergmann
2019-02-20 12:27 ` Arnd Bergmann
2019-02-20 13:16 ` Masami Hiramatsu
2019-02-20 13:16 ` Masami Hiramatsu
2019-02-20 13:18 ` Arnd Bergmann
2019-02-20 13:18 ` Arnd Bergmann
2019-02-20 13:23 ` Masami Hiramatsu
2019-02-20 13:23 ` Masami Hiramatsu
2019-02-21 0:36 ` Sugaya, Taichi
2019-02-21 0:36 ` Sugaya, Taichi
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.