[linux-yocto] [PATCH] Meta: add qemuppc64 bsp config
This is the initial meta data for qemu ppc64 bsp that supports the IBM pseries power* arch with is supported in Qemu. Yes, its not pretty but it works. Signed-off-by: Armin Kuster --- .../bsp/qemu-ppc64/qemu-ppc64-standard.scc |8 + .../cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg | 2778 .../cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.scc |1 + 3 files changed, 2787 insertions(+) create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.scc diff --git a/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc new file mode 100644 index 000..bf48141 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc @@ -0,0 +1,8 @@ +define KMACHINE qemuppc64 +define KTYPE standard +define KARCH powerpc + +include ktypes/standard/standard.scc +branch qemuppc + +include qemu-ppc64.scc diff --git a/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg new file mode 100644 index 000..68c3264 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg @@ -0,0 +1,2778 @@ +CONFIG_PPC64=y + +# +# Processor support +# +CONFIG_PPC_BOOK3S_64=y +# CONFIG_PPC_BOOK3E_64 is not set +CONFIG_GENERIC_CPU=y +# CONFIG_CELL_CPU is not set +# CONFIG_POWER4_CPU is not set +# CONFIG_POWER5_CPU is not set +# CONFIG_POWER6_CPU is not set +# CONFIG_POWER7_CPU is not set +CONFIG_PPC_BOOK3S=y +CONFIG_POWER3=y +CONFIG_POWER4=y +# CONFIG_TUNE_CELL is not set +CONFIG_PPC_FPU=y +CONFIG_ALTIVEC=y +CONFIG_VSX=y +# CONFIG_PPC_ICSWX is not set +CONFIG_PPC_STD_MMU=y +CONFIG_PPC_STD_MMU_64=y +CONFIG_PPC_MM_SLICES=y +CONFIG_PPC_HAVE_PMU_SUPPORT=y +CONFIG_PPC_PERF_CTRS=y +CONFIG_SMP=y +CONFIG_NR_CPUS=2048 +CONFIG_PPC_DOORBELL=y +CONFIG_CPU_BIG_ENDIAN=y +# CONFIG_CPU_LITTLE_ENDIAN is not set +CONFIG_64BIT=y +CONFIG_WORD_SIZE=64 +CONFIG_ARCH_PHYS_ADDR_T_64BIT=y +CONFIG_ARCH_DMA_ADDR_T_64BIT=y +CONFIG_MMU=y +CONFIG_HAVE_SETUP_PER_CPU_AREA=y +CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y +CONFIG_NR_IRQS=512 +CONFIG_STACKTRACE_SUPPORT=y +CONFIG_HAVE_LATENCYTOP_SUPPORT=y +CONFIG_TRACE_IRQFLAGS_SUPPORT=y +CONFIG_LOCKDEP_SUPPORT=y +CONFIG_RWSEM_XCHGADD_ALGORITHM=y +CONFIG_ARCH_HAS_ILOG2_U32=y +CONFIG_ARCH_HAS_ILOG2_U64=y +CONFIG_GENERIC_HWEIGHT=y +CONFIG_PPC=y +# CONFIG_GENERIC_CSUM is not set +CONFIG_EARLY_PRINTK=y +CONFIG_PANIC_TIMEOUT=180 +CONFIG_COMPAT=y +CONFIG_SYSVIPC_COMPAT=y +CONFIG_SCHED_OMIT_FRAME_POINTER=y +CONFIG_ARCH_MAY_HAVE_PC_FDC=y +CONFIG_PPC_OF=y +CONFIG_PPC_UDBG_16550=y +# CONFIG_GENERIC_TBSYNC is not set +CONFIG_AUDIT_ARCH=y +CONFIG_GENERIC_BUG=y +CONFIG_EPAPR_BOOT=y +# CONFIG_DEFAULT_UIMAGE is not set +CONFIG_ARCH_HIBERNATION_POSSIBLE=y +CONFIG_ARCH_SUSPEND_POSSIBLE=y +# CONFIG_PPC_DCR_NATIVE is not set +# CONFIG_PPC_DCR_MMIO is not set +# CONFIG_PPC_OF_PLATFORM_PCI is not set +CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y +CONFIG_ARCH_SUPPORTS_UPROBES=y +CONFIG_PPC_EMULATE_SSTEP=y +CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" +CONFIG_IRQ_WORK=y + +# +# General setup +# +CONFIG_INIT_ENV_ARG_LIMIT=32 +CONFIG_CROSS_COMPILE="" +# CONFIG_COMPILE_TEST is not set +CONFIG_LOCALVERSION="" +CONFIG_LOCALVERSION_AUTO=y +CONFIG_DEFAULT_HOSTNAME="(none)" +CONFIG_SWAP=y +CONFIG_SYSVIPC=y +CONFIG_SYSVIPC_SYSCTL=y +CONFIG_POSIX_MQUEUE=y +CONFIG_POSIX_MQUEUE_SYSCTL=y +# CONFIG_FHANDLE is not set +CONFIG_AUDIT=y +CONFIG_AUDITSYSCALL=y +CONFIG_AUDIT_WATCH=y +CONFIG_AUDIT_TREE=y + +# +# IRQ subsystem +# +CONFIG_GENERIC_IRQ_SHOW=y +CONFIG_GENERIC_IRQ_SHOW_LEVEL=y +CONFIG_IRQ_DOMAIN=y +CONFIG_IRQ_DOMAIN_DEBUG=y +CONFIG_IRQ_FORCED_THREADING=y +CONFIG_SPARSE_IRQ=y +CONFIG_GENERIC_TIME_VSYSCALL_OLD=y +CONFIG_GENERIC_CLOCKEVENTS=y +CONFIG_GENERIC_CLOCKEVENTS_BUILD=y +CONFIG_GENERIC_CMOS_UPDATE=y + +# +# Timers subsystem +# +CONFIG_TICK_ONESHOT=y +CONFIG_NO_HZ_COMMON=y +# CONFIG_HZ_PERIODIC is not set +CONFIG_NO_HZ_IDLE=y +# CONFIG_NO_HZ_FULL is not set +CONFIG_NO_HZ=y +CONFIG_HIGH_RES_TIMERS=y + +# +# CPU/Task time and stats accounting +# +CONFIG_VIRT_CPU_ACCOUNTING=y +# CONFIG_TICK_CPU_ACCOUNTING is not set +CONFIG_VIRT_CPU_ACCOUNTING_NATIVE=y +# CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set +# CONFIG_BSD_PROCESS_ACCT is not set +CONFIG_TASKSTATS=y +CONFIG_TASK_DELAY_ACCT=y +CONFIG_TASK_XACCT=y +CONFIG_TASK_IO_ACCOUNTING=y + +# +# RCU Subsystem +# +CONFIG_TREE_RCU=y +# CONFIG_PREEMPT_RCU is not set +CONFIG_RCU_STALL_COMMON=y +# CONFIG_RCU_USER_QS is not set +CONFIG_RCU_FANOUT=64 +CONFIG_RCU_FANOUT_LEAF=16 +# CONFIG_RCU_FANOUT_EXACT is not set +# CONFIG_RCU_FAST_NO_HZ is not set +# CONFIG_TREE_RCU_TRACE is not set +# CONFIG_RCU_NOCB_CPU is not set +CONFIG_IKCONFIG=y +CONFIG_IKCONFIG_PROC=y +CONFIG_LOG_BUF_SHIFT=17 +CONFIG_ARCH_SUPPORTS_NUMA_BALANCING=y +# CONFIG_NUMA_BALANCING is not set +CONFIG_CGROUPS=y +#
Re: [linux-yocto] [PATCH] Meta: add qemuppc64 bsp config
On 14-08-26 11:05 AM, Armin Kuster wrote: This is the initial meta data for qemu ppc64 bsp that supports the IBM pseries power* arch with is supported in Qemu. Thanks for the patch .. see below for some comments. Yes, its not pretty but it works. Do you have a bootlog capture ? And a list of supported features ? Signed-off-by: Armin Kuster --- .../bsp/qemu-ppc64/qemu-ppc64-standard.scc |8 + .../cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg | 2778 .../cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.scc |1 + 3 files changed, 2787 insertions(+) create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.scc diff --git a/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc new file mode 100644 index 000..bf48141 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc @@ -0,0 +1,8 @@ +define KMACHINE qemuppc64 +define KTYPE standard +define KARCH powerpc + +include ktypes/standard/standard.scc +branch qemuppc + +include qemu-ppc64.scc diff --git a/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg new file mode 100644 index 000..68c3264 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg @@ -0,0 +1,2778 @@ +CONFIG_PPC64=y + +# +# Processor support This looks like a deconfig capture, which is fine as a starting point. But it means that the consistency/policy of the base fragments is not being used. Are we saying that we don't know which ones are platform options ? A visual pass can prune things down quickly .. see below: +# +CONFIG_PPC_BOOK3S_64=y +# CONFIG_PPC_BOOK3E_64 is not set +CONFIG_GENERIC_CPU=y +# CONFIG_CELL_CPU is not set +# CONFIG_POWER4_CPU is not set +# CONFIG_POWER5_CPU is not set +# CONFIG_POWER6_CPU is not set +# CONFIG_POWER7_CPU is not set +CONFIG_PPC_BOOK3S=y +CONFIG_POWER3=y +CONFIG_POWER4=y +# CONFIG_TUNE_CELL is not set +CONFIG_PPC_FPU=y +CONFIG_ALTIVEC=y +CONFIG_VSX=y +# CONFIG_PPC_ICSWX is not set +CONFIG_PPC_STD_MMU=y +CONFIG_PPC_STD_MMU_64=y +CONFIG_PPC_MM_SLICES=y +CONFIG_PPC_HAVE_PMU_SUPPORT=y +CONFIG_PPC_PERF_CTRS=y +CONFIG_SMP=y +CONFIG_NR_CPUS=2048 +CONFIG_PPC_DOORBELL=y +CONFIG_CPU_BIG_ENDIAN=y +# CONFIG_CPU_LITTLE_ENDIAN is not set +CONFIG_64BIT=y +CONFIG_WORD_SIZE=64 +CONFIG_ARCH_PHYS_ADDR_T_64BIT=y +CONFIG_ARCH_DMA_ADDR_T_64BIT=y +CONFIG_MMU=y +CONFIG_HAVE_SETUP_PER_CPU_AREA=y +CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y +CONFIG_NR_IRQS=512 +CONFIG_STACKTRACE_SUPPORT=y +CONFIG_HAVE_LATENCYTOP_SUPPORT=y +CONFIG_TRACE_IRQFLAGS_SUPPORT=y +CONFIG_LOCKDEP_SUPPORT=y +CONFIG_RWSEM_XCHGADD_ALGORITHM=y +CONFIG_ARCH_HAS_ILOG2_U32=y +CONFIG_ARCH_HAS_ILOG2_U64=y +CONFIG_GENERIC_HWEIGHT=y +CONFIG_PPC=y +# CONFIG_GENERIC_CSUM is not set +CONFIG_EARLY_PRINTK=y Things like early printk, are not in board h/w fragments. +CONFIG_PANIC_TIMEOUT=180 +CONFIG_COMPAT=y +CONFIG_SYSVIPC_COMPAT=y +CONFIG_SCHED_OMIT_FRAME_POINTER=y +CONFIG_ARCH_MAY_HAVE_PC_FDC=y +CONFIG_PPC_OF=y +CONFIG_PPC_UDBG_16550=y +# CONFIG_GENERIC_TBSYNC is not set +CONFIG_AUDIT_ARCH=y +CONFIG_GENERIC_BUG=y +CONFIG_EPAPR_BOOT=y +# CONFIG_DEFAULT_UIMAGE is not set +CONFIG_ARCH_HIBERNATION_POSSIBLE=y +CONFIG_ARCH_SUSPEND_POSSIBLE=y +# CONFIG_PPC_DCR_NATIVE is not set +# CONFIG_PPC_DCR_MMIO is not set +# CONFIG_PPC_OF_PLATFORM_PCI is not set +CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y +CONFIG_ARCH_SUPPORTS_UPROBES=y +CONFIG_PPC_EMULATE_SSTEP=y +CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" +CONFIG_IRQ_WORK=y + +# +# General setup +# +CONFIG_INIT_ENV_ARG_LIMIT=32 +CONFIG_CROSS_COMPILE="" +# CONFIG_COMPILE_TEST is not set +CONFIG_LOCALVERSION="" +CONFIG_LOCALVERSION_AUTO=y +CONFIG_DEFAULT_HOSTNAME="(none)" +CONFIG_SWAP=y +CONFIG_SYSVIPC=y +CONFIG_SYSVIPC_SYSCTL=y +CONFIG_POSIX_MQUEUE=y +CONFIG_POSIX_MQUEUE_SYSCTL=y +# CONFIG_FHANDLE is not set +CONFIG_AUDIT=y +CONFIG_AUDITSYSCALL=y +CONFIG_AUDIT_WATCH=y +CONFIG_AUDIT_TREE=y The above block are all non-hw options. + +# +# IRQ subsystem +# +CONFIG_GENERIC_IRQ_SHOW=y +CONFIG_GENERIC_IRQ_SHOW_LEVEL=y +CONFIG_IRQ_DOMAIN=y +CONFIG_IRQ_DOMAIN_DEBUG=y +CONFIG_IRQ_FORCED_THREADING=y +CONFIG_SPARSE_IRQ=y +CONFIG_GENERIC_TIME_VSYSCALL_OLD=y +CONFIG_GENERIC_CLOCKEVENTS=y +CONFIG_GENERIC_CLOCKEVENTS_BUILD=y +CONFIG_GENERIC_CMOS_UPDATE=y + +# +# Timers subsystem +# +CONFIG_TICK_ONESHOT=y +CONFIG_NO_HZ_COMMON=y +# CONFIG_HZ_PERIODIC is not set +CONFIG_NO_HZ_IDLE=y +# CONFIG_NO_HZ_FULL is not set +CONFIG_NO_HZ=y +CONFIG_HIGH_RES_TIMERS=y + +# +# CPU/Task time and stats accounting +# +CONFIG_VIRT_CPU_ACCOUNTING=y +# CONFIG_TICK_CPU_ACCOUNTING is not set +CONFIG_VIRT_CPU_ACCOUNTING_NATIVE=y +# CONFIG_VIRT_CPU_ACCOUNTING_GEN is not set +# CONFIG_BSD_PROCESS_ACCT is not set +CONFIG_TASKSTATS=y
Re: [linux-yocto] [PATCH] Meta: add qemuppc64 bsp config
On 08/26/2014 10:04 AM, Bruce Ashfield wrote: On 14-08-26 11:05 AM, Armin Kuster wrote: This is the initial meta data for qemu ppc64 bsp that supports the IBM pseries power* arch with is supported in Qemu. Thanks for the patch .. see below for some comments. Yes, its not pretty but it works. Do you have a bootlog capture ? I can on getting one. is this normally need ( process question). And a list of supported features ? is the a doc on what is meant by features? Signed-off-by: Armin Kuster --- .../bsp/qemu-ppc64/qemu-ppc64-standard.scc |8 + .../cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg | 2778 .../cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.scc |1 + 3 files changed, 2787 insertions(+) create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.scc diff --git a/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc new file mode 100644 index 000..bf48141 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc @@ -0,0 +1,8 @@ +define KMACHINE qemuppc64 +define KTYPE standard +define KARCH powerpc + +include ktypes/standard/standard.scc +branch qemuppc + +include qemu-ppc64.scc diff --git a/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg new file mode 100644 index 000..68c3264 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg @@ -0,0 +1,2778 @@ +CONFIG_PPC64=y + +# +# Processor support This looks like a deconfig capture, which is fine as a starting point. correct. easiest thing to do for now. But it means that the consistency/policy of the base fragments is not being used. this is the goal I hope to achieve as I learn this process. Are we saying that we don't know which ones are platform options ? A visual pass can prune things down quickly .. see below: I will take out my chainsaw and do a bit of trimming and clean up. +# +CONFIG_PPC_BOOK3S_64=y +# CONFIG_PPC_BOOK3E_64 is not set +CONFIG_GENERIC_CPU=y +# CONFIG_CELL_CPU is not set +# CONFIG_POWER4_CPU is not set +# CONFIG_POWER5_CPU is not set +# CONFIG_POWER6_CPU is not set +# CONFIG_POWER7_CPU is not set +CONFIG_PPC_BOOK3S=y +CONFIG_POWER3=y +CONFIG_POWER4=y +# CONFIG_TUNE_CELL is not set +CONFIG_PPC_FPU=y +CONFIG_ALTIVEC=y +CONFIG_VSX=y +# CONFIG_PPC_ICSWX is not set +CONFIG_PPC_STD_MMU=y +CONFIG_PPC_STD_MMU_64=y +CONFIG_PPC_MM_SLICES=y +CONFIG_PPC_HAVE_PMU_SUPPORT=y +CONFIG_PPC_PERF_CTRS=y +CONFIG_SMP=y +CONFIG_NR_CPUS=2048 +CONFIG_PPC_DOORBELL=y +CONFIG_CPU_BIG_ENDIAN=y +# CONFIG_CPU_LITTLE_ENDIAN is not set +CONFIG_64BIT=y +CONFIG_WORD_SIZE=64 +CONFIG_ARCH_PHYS_ADDR_T_64BIT=y +CONFIG_ARCH_DMA_ADDR_T_64BIT=y +CONFIG_MMU=y +CONFIG_HAVE_SETUP_PER_CPU_AREA=y +CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y +CONFIG_NR_IRQS=512 +CONFIG_STACKTRACE_SUPPORT=y +CONFIG_HAVE_LATENCYTOP_SUPPORT=y +CONFIG_TRACE_IRQFLAGS_SUPPORT=y +CONFIG_LOCKDEP_SUPPORT=y +CONFIG_RWSEM_XCHGADD_ALGORITHM=y +CONFIG_ARCH_HAS_ILOG2_U32=y +CONFIG_ARCH_HAS_ILOG2_U64=y +CONFIG_GENERIC_HWEIGHT=y +CONFIG_PPC=y +# CONFIG_GENERIC_CSUM is not set +CONFIG_EARLY_PRINTK=y Things like early printk, are not in board h/w fragments. ok +CONFIG_PANIC_TIMEOUT=180 +CONFIG_COMPAT=y +CONFIG_SYSVIPC_COMPAT=y +CONFIG_SCHED_OMIT_FRAME_POINTER=y +CONFIG_ARCH_MAY_HAVE_PC_FDC=y +CONFIG_PPC_OF=y +CONFIG_PPC_UDBG_16550=y +# CONFIG_GENERIC_TBSYNC is not set +CONFIG_AUDIT_ARCH=y +CONFIG_GENERIC_BUG=y +CONFIG_EPAPR_BOOT=y +# CONFIG_DEFAULT_UIMAGE is not set +CONFIG_ARCH_HIBERNATION_POSSIBLE=y +CONFIG_ARCH_SUSPEND_POSSIBLE=y +# CONFIG_PPC_DCR_NATIVE is not set +# CONFIG_PPC_DCR_MMIO is not set +# CONFIG_PPC_OF_PLATFORM_PCI is not set +CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y +CONFIG_ARCH_SUPPORTS_UPROBES=y +CONFIG_PPC_EMULATE_SSTEP=y +CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" +CONFIG_IRQ_WORK=y + +# +# General setup +# +CONFIG_INIT_ENV_ARG_LIMIT=32 +CONFIG_CROSS_COMPILE="" +# CONFIG_COMPILE_TEST is not set +CONFIG_LOCALVERSION="" +CONFIG_LOCALVERSION_AUTO=y +CONFIG_DEFAULT_HOSTNAME="(none)" +CONFIG_SWAP=y +CONFIG_SYSVIPC=y +CONFIG_SYSVIPC_SYSCTL=y +CONFIG_POSIX_MQUEUE=y +CONFIG_POSIX_MQUEUE_SYSCTL=y +# CONFIG_FHANDLE is not set +CONFIG_AUDIT=y +CONFIG_AUDITSYSCALL=y +CONFIG_AUDIT_WATCH=y +CONFIG_AUDIT_TREE=y The above block are all non-hw options. ok. is this where I need to hunt down which file contains that fragment or do you mean this is something a user adds with menuconfig? + +# +# IRQ subsystem +# +CONFIG_GENERIC_IRQ_SHOW=y +CONFIG_GENERIC_IRQ_SHOW_LEVEL=y +CONFIG_IRQ_DOMAIN=y +CONFIG_IRQ_DOMAIN_DEBUG=y +CONFIG_IRQ_FORCED_THREADING=y +CONFIG_SPARSE_IRQ=y +CONFIG_GENERIC_TIME_VSYSCALL_OLD=y +CONFIG_GENERIC_CLOCKEVENTS=y +CONFIG_GENERIC_CLOCKEVENTS_BUILD=y +CONF
Re: [linux-yocto] [PATCH] Meta: add qemuppc64 bsp config
On 2014-08-26, 8:25 PM, akuster808 wrote: On 08/26/2014 10:04 AM, Bruce Ashfield wrote: On 14-08-26 11:05 AM, Armin Kuster wrote: This is the initial meta data for qemu ppc64 bsp that supports the IBM pseries power* arch with is supported in Qemu. Thanks for the patch .. see below for some comments. Yes, its not pretty but it works. Do you have a bootlog capture ? I can on getting one. is this normally need ( process question). There's no firm process, but it is something that I've asked for over the years, since it gives us a good reference to what was working when the BSP was first introduced. And a list of supported features ? is the a doc on what is meant by features? It's mainly features from the point of view of the h/w. i.e. what ethernet is used (emulated or not), clock sources, etc. The yocto reference BSPs capture some of this in the README files. Again, no hard and fast rules .. but the more we know, the more I can not break the board with merges, and when someone wanders by later, they'll know what to expect. Signed-off-by: Armin Kuster --- .../bsp/qemu-ppc64/qemu-ppc64-standard.scc |8 + .../cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg | 2778 .../cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.scc |1 + 3 files changed, 2787 insertions(+) create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.scc diff --git a/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc new file mode 100644 index 000..bf48141 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc @@ -0,0 +1,8 @@ +define KMACHINE qemuppc64 +define KTYPE standard +define KARCH powerpc + +include ktypes/standard/standard.scc +branch qemuppc + +include qemu-ppc64.scc diff --git a/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg new file mode 100644 index 000..68c3264 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg @@ -0,0 +1,2778 @@ +CONFIG_PPC64=y + +# +# Processor support This looks like a deconfig capture, which is fine as a starting point. correct. easiest thing to do for now. But it means that the consistency/policy of the base fragments is not being used. this is the goal I hope to achieve as I learn this process. Are we saying that we don't know which ones are platform options ? A visual pass can prune things down quickly .. see below: I will take out my chainsaw and do a bit of trimming and clean up. Excellent :) +# +CONFIG_PPC_BOOK3S_64=y +# CONFIG_PPC_BOOK3E_64 is not set +CONFIG_GENERIC_CPU=y +# CONFIG_CELL_CPU is not set +# CONFIG_POWER4_CPU is not set +# CONFIG_POWER5_CPU is not set +# CONFIG_POWER6_CPU is not set +# CONFIG_POWER7_CPU is not set +CONFIG_PPC_BOOK3S=y +CONFIG_POWER3=y +CONFIG_POWER4=y +# CONFIG_TUNE_CELL is not set +CONFIG_PPC_FPU=y +CONFIG_ALTIVEC=y +CONFIG_VSX=y +# CONFIG_PPC_ICSWX is not set +CONFIG_PPC_STD_MMU=y +CONFIG_PPC_STD_MMU_64=y +CONFIG_PPC_MM_SLICES=y +CONFIG_PPC_HAVE_PMU_SUPPORT=y +CONFIG_PPC_PERF_CTRS=y +CONFIG_SMP=y +CONFIG_NR_CPUS=2048 +CONFIG_PPC_DOORBELL=y +CONFIG_CPU_BIG_ENDIAN=y +# CONFIG_CPU_LITTLE_ENDIAN is not set +CONFIG_64BIT=y +CONFIG_WORD_SIZE=64 +CONFIG_ARCH_PHYS_ADDR_T_64BIT=y +CONFIG_ARCH_DMA_ADDR_T_64BIT=y +CONFIG_MMU=y +CONFIG_HAVE_SETUP_PER_CPU_AREA=y +CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y +CONFIG_NR_IRQS=512 +CONFIG_STACKTRACE_SUPPORT=y +CONFIG_HAVE_LATENCYTOP_SUPPORT=y +CONFIG_TRACE_IRQFLAGS_SUPPORT=y +CONFIG_LOCKDEP_SUPPORT=y +CONFIG_RWSEM_XCHGADD_ALGORITHM=y +CONFIG_ARCH_HAS_ILOG2_U32=y +CONFIG_ARCH_HAS_ILOG2_U64=y +CONFIG_GENERIC_HWEIGHT=y +CONFIG_PPC=y +# CONFIG_GENERIC_CSUM is not set +CONFIG_EARLY_PRINTK=y Things like early printk, are not in board h/w fragments. ok +CONFIG_PANIC_TIMEOUT=180 +CONFIG_COMPAT=y +CONFIG_SYSVIPC_COMPAT=y +CONFIG_SCHED_OMIT_FRAME_POINTER=y +CONFIG_ARCH_MAY_HAVE_PC_FDC=y +CONFIG_PPC_OF=y +CONFIG_PPC_UDBG_16550=y +# CONFIG_GENERIC_TBSYNC is not set +CONFIG_AUDIT_ARCH=y +CONFIG_GENERIC_BUG=y +CONFIG_EPAPR_BOOT=y +# CONFIG_DEFAULT_UIMAGE is not set +CONFIG_ARCH_HIBERNATION_POSSIBLE=y +CONFIG_ARCH_SUSPEND_POSSIBLE=y +# CONFIG_PPC_DCR_NATIVE is not set +# CONFIG_PPC_DCR_MMIO is not set +# CONFIG_PPC_OF_PLATFORM_PCI is not set +CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y +CONFIG_ARCH_SUPPORTS_UPROBES=y +CONFIG_PPC_EMULATE_SSTEP=y +CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" +CONFIG_IRQ_WORK=y + +# +# General setup +# +CONFIG_INIT_ENV_ARG_LIMIT=32 +CONFIG_CROSS_COMPILE="" +# CONFIG_COMPILE_TEST is not set +CONFIG_LOCALVERSION="" +CONFIG_LOCALVERSION_AUTO=y +CONFIG_DEFAULT_HOSTNAME="(none)" +CONFIG_SWAP=y +CONFIG_SYSVIPC=y +CONFIG_SYSVIPC_SYSCTL=y +CONFIG_POSIX_MQUEUE=y +CONFIG_POSIX_MQUEUE_S
Re: [linux-yocto] [PATCH] Meta: add qemuppc64 bsp config
On 08/26/2014 09:39 PM, Bruce Ashfield wrote: On 2014-08-26, 8:25 PM, akuster808 wrote: On 08/26/2014 10:04 AM, Bruce Ashfield wrote: On 14-08-26 11:05 AM, Armin Kuster wrote: This is the initial meta data for qemu ppc64 bsp that supports the IBM pseries power* arch with is supported in Qemu. Thanks for the patch .. see below for some comments. Yes, its not pretty but it works. Do you have a bootlog capture ? I can on getting one. is this normally need ( process question). There's no firm process, but it is something that I've asked for over the years, since it gives us a good reference to what was working when the BSP was first introduced. I am attaching the dmesg. I could not get QEMU to behave to give me a serial console. could be an open firmware thing. I have posted a 'V2' of meta changes. And a list of supported features ? is the a doc on what is meant by features? It's mainly features from the point of view of the h/w. i.e. what ethernet is used (emulated or not), clock sources, etc. The yocto reference BSPs capture some of this in the README files. Again, no hard and fast rules .. but the more we know, the more I can not break the board with merges, and when someone wanders by later, they'll know what to expect. Enternet SCSI USB VGA (but X currently crashes) Signed-off-by: Armin Kuster --- .../bsp/qemu-ppc64/qemu-ppc64-standard.scc |8 + .../cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg | 2778 .../cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.scc |1 + 3 files changed, 2787 insertions(+) create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.scc diff --git a/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc new file mode 100644 index 000..bf48141 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc @@ -0,0 +1,8 @@ +define KMACHINE qemuppc64 +define KTYPE standard +define KARCH powerpc + +include ktypes/standard/standard.scc +branch qemuppc + +include qemu-ppc64.scc diff --git a/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg new file mode 100644 index 000..68c3264 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg @@ -0,0 +1,2778 @@ +CONFIG_PPC64=y + +# +# Processor support This looks like a deconfig capture, which is fine as a starting point. correct. easiest thing to do for now. But it means that the consistency/policy of the base fragments is not being used. this is the goal I hope to achieve as I learn this process. Are we saying that we don't know which ones are platform options ? A visual pass can prune things down quickly .. see below: I will take out my chainsaw and do a bit of trimming and clean up. Excellent :) +# +CONFIG_PPC_BOOK3S_64=y +# CONFIG_PPC_BOOK3E_64 is not set +CONFIG_GENERIC_CPU=y +# CONFIG_CELL_CPU is not set +# CONFIG_POWER4_CPU is not set +# CONFIG_POWER5_CPU is not set +# CONFIG_POWER6_CPU is not set +# CONFIG_POWER7_CPU is not set +CONFIG_PPC_BOOK3S=y +CONFIG_POWER3=y +CONFIG_POWER4=y +# CONFIG_TUNE_CELL is not set +CONFIG_PPC_FPU=y +CONFIG_ALTIVEC=y +CONFIG_VSX=y +# CONFIG_PPC_ICSWX is not set +CONFIG_PPC_STD_MMU=y +CONFIG_PPC_STD_MMU_64=y +CONFIG_PPC_MM_SLICES=y +CONFIG_PPC_HAVE_PMU_SUPPORT=y +CONFIG_PPC_PERF_CTRS=y +CONFIG_SMP=y +CONFIG_NR_CPUS=2048 +CONFIG_PPC_DOORBELL=y +CONFIG_CPU_BIG_ENDIAN=y +# CONFIG_CPU_LITTLE_ENDIAN is not set +CONFIG_64BIT=y +CONFIG_WORD_SIZE=64 +CONFIG_ARCH_PHYS_ADDR_T_64BIT=y +CONFIG_ARCH_DMA_ADDR_T_64BIT=y +CONFIG_MMU=y +CONFIG_HAVE_SETUP_PER_CPU_AREA=y +CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y +CONFIG_NR_IRQS=512 +CONFIG_STACKTRACE_SUPPORT=y +CONFIG_HAVE_LATENCYTOP_SUPPORT=y +CONFIG_TRACE_IRQFLAGS_SUPPORT=y +CONFIG_LOCKDEP_SUPPORT=y +CONFIG_RWSEM_XCHGADD_ALGORITHM=y +CONFIG_ARCH_HAS_ILOG2_U32=y +CONFIG_ARCH_HAS_ILOG2_U64=y +CONFIG_GENERIC_HWEIGHT=y +CONFIG_PPC=y +# CONFIG_GENERIC_CSUM is not set +CONFIG_EARLY_PRINTK=y Things like early printk, are not in board h/w fragments. ok +CONFIG_PANIC_TIMEOUT=180 +CONFIG_COMPAT=y +CONFIG_SYSVIPC_COMPAT=y +CONFIG_SCHED_OMIT_FRAME_POINTER=y +CONFIG_ARCH_MAY_HAVE_PC_FDC=y +CONFIG_PPC_OF=y +CONFIG_PPC_UDBG_16550=y +# CONFIG_GENERIC_TBSYNC is not set +CONFIG_AUDIT_ARCH=y +CONFIG_GENERIC_BUG=y +CONFIG_EPAPR_BOOT=y +# CONFIG_DEFAULT_UIMAGE is not set +CONFIG_ARCH_HIBERNATION_POSSIBLE=y +CONFIG_ARCH_SUSPEND_POSSIBLE=y +# CONFIG_PPC_DCR_NATIVE is not set +# CONFIG_PPC_DCR_MMIO is not set +# CONFIG_PPC_OF_PLATFORM_PCI is not set +CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y +CONFIG_ARCH_SUPPORTS_UPROBES=y +CONFIG_PPC_EMULATE_SSTEP=y +CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" +CONFIG_IRQ_WORK=y + +# +# General setup +# +CONFIG_INIT_
Re: [linux-yocto] [PATCH] Meta: add qemuppc64 bsp config
On 14-08-28 10:29 AM, akuster808 wrote: On 08/26/2014 09:39 PM, Bruce Ashfield wrote: On 2014-08-26, 8:25 PM, akuster808 wrote: On 08/26/2014 10:04 AM, Bruce Ashfield wrote: On 14-08-26 11:05 AM, Armin Kuster wrote: This is the initial meta data for qemu ppc64 bsp that supports the IBM pseries power* arch with is supported in Qemu. Thanks for the patch .. see below for some comments. Yes, its not pretty but it works. Do you have a bootlog capture ? I can on getting one. is this normally need ( process question). There's no firm process, but it is something that I've asked for over the years, since it gives us a good reference to what was working when the BSP was first introduced. I am attaching the dmesg. I could not get QEMU to behave to give me a serial console. could be an open firmware thing. I have posted a 'V2' of meta changes. Nice. I'll have a look shortly. One other question .. any other tweaks that I need to get the right qemu support added ? I'll do a build and boot test if I have the right instructions. Cheers, Bruce And a list of supported features ? is the a doc on what is meant by features? It's mainly features from the point of view of the h/w. i.e. what ethernet is used (emulated or not), clock sources, etc. The yocto reference BSPs capture some of this in the README files. Again, no hard and fast rules .. but the more we know, the more I can not break the board with merges, and when someone wanders by later, they'll know what to expect. Enternet SCSI USB VGA (but X currently crashes) Signed-off-by: Armin Kuster --- .../bsp/qemu-ppc64/qemu-ppc64-standard.scc |8 + .../cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg | 2778 .../cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.scc |1 + 3 files changed, 2787 insertions(+) create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.scc diff --git a/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc new file mode 100644 index 000..bf48141 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc @@ -0,0 +1,8 @@ +define KMACHINE qemuppc64 +define KTYPE standard +define KARCH powerpc + +include ktypes/standard/standard.scc +branch qemuppc + +include qemu-ppc64.scc diff --git a/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg new file mode 100644 index 000..68c3264 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg @@ -0,0 +1,2778 @@ +CONFIG_PPC64=y + +# +# Processor support This looks like a deconfig capture, which is fine as a starting point. correct. easiest thing to do for now. But it means that the consistency/policy of the base fragments is not being used. this is the goal I hope to achieve as I learn this process. Are we saying that we don't know which ones are platform options ? A visual pass can prune things down quickly .. see below: I will take out my chainsaw and do a bit of trimming and clean up. Excellent :) +# +CONFIG_PPC_BOOK3S_64=y +# CONFIG_PPC_BOOK3E_64 is not set +CONFIG_GENERIC_CPU=y +# CONFIG_CELL_CPU is not set +# CONFIG_POWER4_CPU is not set +# CONFIG_POWER5_CPU is not set +# CONFIG_POWER6_CPU is not set +# CONFIG_POWER7_CPU is not set +CONFIG_PPC_BOOK3S=y +CONFIG_POWER3=y +CONFIG_POWER4=y +# CONFIG_TUNE_CELL is not set +CONFIG_PPC_FPU=y +CONFIG_ALTIVEC=y +CONFIG_VSX=y +# CONFIG_PPC_ICSWX is not set +CONFIG_PPC_STD_MMU=y +CONFIG_PPC_STD_MMU_64=y +CONFIG_PPC_MM_SLICES=y +CONFIG_PPC_HAVE_PMU_SUPPORT=y +CONFIG_PPC_PERF_CTRS=y +CONFIG_SMP=y +CONFIG_NR_CPUS=2048 +CONFIG_PPC_DOORBELL=y +CONFIG_CPU_BIG_ENDIAN=y +# CONFIG_CPU_LITTLE_ENDIAN is not set +CONFIG_64BIT=y +CONFIG_WORD_SIZE=64 +CONFIG_ARCH_PHYS_ADDR_T_64BIT=y +CONFIG_ARCH_DMA_ADDR_T_64BIT=y +CONFIG_MMU=y +CONFIG_HAVE_SETUP_PER_CPU_AREA=y +CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y +CONFIG_NR_IRQS=512 +CONFIG_STACKTRACE_SUPPORT=y +CONFIG_HAVE_LATENCYTOP_SUPPORT=y +CONFIG_TRACE_IRQFLAGS_SUPPORT=y +CONFIG_LOCKDEP_SUPPORT=y +CONFIG_RWSEM_XCHGADD_ALGORITHM=y +CONFIG_ARCH_HAS_ILOG2_U32=y +CONFIG_ARCH_HAS_ILOG2_U64=y +CONFIG_GENERIC_HWEIGHT=y +CONFIG_PPC=y +# CONFIG_GENERIC_CSUM is not set +CONFIG_EARLY_PRINTK=y Things like early printk, are not in board h/w fragments. ok +CONFIG_PANIC_TIMEOUT=180 +CONFIG_COMPAT=y +CONFIG_SYSVIPC_COMPAT=y +CONFIG_SCHED_OMIT_FRAME_POINTER=y +CONFIG_ARCH_MAY_HAVE_PC_FDC=y +CONFIG_PPC_OF=y +CONFIG_PPC_UDBG_16550=y +# CONFIG_GENERIC_TBSYNC is not set +CONFIG_AUDIT_ARCH=y +CONFIG_GENERIC_BUG=y +CONFIG_EPAPR_BOOT=y +# CONFIG_DEFAULT_UIMAGE is not set +CONFIG_ARCH_HIBERNATION_POSSIBLE=y +CONFIG_ARCH_SUSPEND_POSSIBLE=y +# CONFIG_PPC_DCR_NATIVE is not set +# CONFIG_PPC_DCR_MMIO is not set +# CONFIG_PPC_O
Re: [linux-yocto] [PATCH] Meta: add qemuppc64 bsp config
On 08/28/2014 07:40 AM, Bruce Ashfield wrote: On 14-08-28 10:29 AM, akuster808 wrote: On 08/26/2014 09:39 PM, Bruce Ashfield wrote: On 2014-08-26, 8:25 PM, akuster808 wrote: On 08/26/2014 10:04 AM, Bruce Ashfield wrote: On 14-08-26 11:05 AM, Armin Kuster wrote: This is the initial meta data for qemu ppc64 bsp that supports the IBM pseries power* arch with is supported in Qemu. Thanks for the patch .. see below for some comments. Yes, its not pretty but it works. Do you have a bootlog capture ? I can on getting one. is this normally need ( process question). There's no firm process, but it is something that I've asked for over the years, since it gives us a good reference to what was working when the BSP was first introduced. I am attaching the dmesg. I could not get QEMU to behave to give me a serial console. could be an open firmware thing. I have posted a 'V2' of meta changes. Nice. I'll have a look shortly. One other question .. any other tweaks that I need to get the right qemu support added ? I'll do a build and boot test if I have the right instructions. What is missing is the machine config and update linux-yocto.bb file and I have runqemu script changes. I can send all those along too. The tune files are in OE already. The order of submission I am taking is tune files, yocto-linux, linux.bb, machine config then scripts. This seems to be the order of dependence for me. First time doing this, maybe there is a more appropriate order??? I can send you everything I have. regards, Armin Cheers, Bruce And a list of supported features ? is the a doc on what is meant by features? It's mainly features from the point of view of the h/w. i.e. what ethernet is used (emulated or not), clock sources, etc. The yocto reference BSPs capture some of this in the README files. Again, no hard and fast rules .. but the more we know, the more I can not break the board with merges, and when someone wanders by later, they'll know what to expect. Enternet SCSI USB VGA (but X currently crashes) Signed-off-by: Armin Kuster --- .../bsp/qemu-ppc64/qemu-ppc64-standard.scc |8 + .../cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg | 2778 .../cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.scc |1 + 3 files changed, 2787 insertions(+) create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg create mode 100644 meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.scc diff --git a/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc new file mode 100644 index 000..bf48141 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64-standard.scc @@ -0,0 +1,8 @@ +define KMACHINE qemuppc64 +define KTYPE standard +define KARCH powerpc + +include ktypes/standard/standard.scc +branch qemuppc + +include qemu-ppc64.scc diff --git a/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg new file mode 100644 index 000..68c3264 --- /dev/null +++ b/meta/cfg/kernel-cache/bsp/qemu-ppc64/qemu-ppc64.cfg @@ -0,0 +1,2778 @@ +CONFIG_PPC64=y + +# +# Processor support This looks like a deconfig capture, which is fine as a starting point. correct. easiest thing to do for now. But it means that the consistency/policy of the base fragments is not being used. this is the goal I hope to achieve as I learn this process. Are we saying that we don't know which ones are platform options ? A visual pass can prune things down quickly .. see below: I will take out my chainsaw and do a bit of trimming and clean up. Excellent :) +# +CONFIG_PPC_BOOK3S_64=y +# CONFIG_PPC_BOOK3E_64 is not set +CONFIG_GENERIC_CPU=y +# CONFIG_CELL_CPU is not set +# CONFIG_POWER4_CPU is not set +# CONFIG_POWER5_CPU is not set +# CONFIG_POWER6_CPU is not set +# CONFIG_POWER7_CPU is not set +CONFIG_PPC_BOOK3S=y +CONFIG_POWER3=y +CONFIG_POWER4=y +# CONFIG_TUNE_CELL is not set +CONFIG_PPC_FPU=y +CONFIG_ALTIVEC=y +CONFIG_VSX=y +# CONFIG_PPC_ICSWX is not set +CONFIG_PPC_STD_MMU=y +CONFIG_PPC_STD_MMU_64=y +CONFIG_PPC_MM_SLICES=y +CONFIG_PPC_HAVE_PMU_SUPPORT=y +CONFIG_PPC_PERF_CTRS=y +CONFIG_SMP=y +CONFIG_NR_CPUS=2048 +CONFIG_PPC_DOORBELL=y +CONFIG_CPU_BIG_ENDIAN=y +# CONFIG_CPU_LITTLE_ENDIAN is not set +CONFIG_64BIT=y +CONFIG_WORD_SIZE=64 +CONFIG_ARCH_PHYS_ADDR_T_64BIT=y +CONFIG_ARCH_DMA_ADDR_T_64BIT=y +CONFIG_MMU=y +CONFIG_HAVE_SETUP_PER_CPU_AREA=y +CONFIG_NEED_PER_CPU_EMBED_FIRST_CHUNK=y +CONFIG_NR_IRQS=512 +CONFIG_STACKTRACE_SUPPORT=y +CONFIG_HAVE_LATENCYTOP_SUPPORT=y +CONFIG_TRACE_IRQFLAGS_SUPPORT=y +CONFIG_LOCKDEP_SUPPORT=y +CONFIG_RWSEM_XCHGADD_ALGORITHM=y +CONFIG_ARCH_HAS_ILOG2_U32=y +CONFIG_ARCH_HAS_ILOG2_U64=y +CONFIG_GENERIC_HWEIGHT=y +CONFIG_PPC=y +# CONFIG_GENERIC_CSUM is not set +CONFIG_EARLY_PRINTK=y Things like early printk, ar
