Re: Combining defconfigs for 44x based boards
Hi, On Thu, 9 Sep 2010 15:17:10 -0700 Tirumala Marri wrote: > > [Marri]That is kind of true. Can we create new defconfigs then ? > I am trying to check-in new defconfig. Just make sure that it is minimal by using "make savedefconfig". This will create a file "defconfig" in the current directory which should have the minimal amount of stuff in it to reproduce the current .config. -- Cheers, Stephen Rothwells...@canb.auug.org.au http://www.canb.auug.org.au/~sfr/ pgpha4DcBvzEZ.pgp Description: PGP signature ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
RE: Combining defconfigs for 44x based boards
> On Thu, 9 Sep 2010 09:49:14 -0700 > Tirumala Marri wrote: > > > [Marri] Great we already have it. We should remove the defconfigs > > under 44x then ? > > I'd rather we didn't. I thought Linus' beef was over the churn in the > defconfigs, not the fact that they exist. The 44x defconfigs change > very rarely. [Marri]That is kind of true. Can we create new defconfigs then ? I am trying to check-in new defconfig. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: Combining defconfigs for 44x based boards
On Thu, 9 Sep 2010 09:49:14 -0700 Tirumala Marri wrote: > [Marri] Great we already have it. We should remove the defconfigs > under 44x then ? I'd rather we didn't. I thought Linus' beef was over the churn in the defconfigs, not the fact that they exist. The 44x defconfigs change very rarely. Cheers, Sean ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
RE: Combining defconfigs for 44x based boards
> > We already have arch/powerpc/configs/ppc40x_defconfig and > arch/powerpc/configs/ppc44x_defconfig in mainline. > > What's wrong with using these? [Marri] Great we already have it. We should remove the defconfigs under 44x then ? Regards, Marri ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: Combining defconfigs for 44x based boards
Dear Tirumala Marri, In message <49073d172310031addb3aa7d08a60...@mail.gmail.com> you wrote: > > I am thinking that we can combine arches, Canyonlands, glacier, redwood > and eiger can be combined as ppc46x_defconfig. We already have arch/powerpc/configs/ppc40x_defconfig and arch/powerpc/configs/ppc44x_defconfig in mainline. What's wrong with using these? Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de CONSUMER NOTICE: Because of the "Uncertainty Principle," It Is Impossible for the Consumer to Find Out at the Same Time Both Precisely Where This Product Is and How Fast It Is Moving. ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: Combining defconfigs for 44x based boards
On Wed, Sep 08, 2010 at 07:11:11PM -0700, Tirumala Marri wrote: > > > > On Wed, Sep 08, 2010 at 03:40:37PM -0700, Tirumala Marri wrote: > > > Is anyone working on Linus suggestion to combine the defconfigs under > > 44x > > > or 4xx ? > > > > Do you mean ppc44x_defconfig? Already there. > No it is not there yet. I should have said "Linus suggestion about > defconfigs in ARM mailing list". ARM and powerpc are somewhat different in this aspect, since ARM traditionally has not been able to build multiplatform kernels (especially not multi-soc-family kernels). Powerpc can build a kernel that will boot on all machines of a certain class (server, fsl-booke, ibm-booke, ppc32). So there's not really a whole lot of reason to have the custom per-board defconfigs in the kernel tree any more. For specific products it might still make sense for a vendor to make a custom minimal defconfig, but that doesn't mean it's a requirement to have them in the upstream repository. -Olof ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
RE: Combining defconfigs for 44x based boards
> > Linus made a suggestion to that effect? If so, I missed it. Have a > pointer? > I am thinking that we can combine arches, Canyonlands, glacier, redwood and eiger can be combined as ppc46x_defconfig. here is the defconfig example --- # # Automatically generated make config: don't edit # Linux kernel version: 2.6.36-rc2 # Thu Sep 2 11:25:03 2010 # # CONFIG_PPC64 is not set # # Processor support # CONFIG_44x=y CONFIG_PPC_FPU=y CONFIG_4xx=y CONFIG_BOOKE=y CONFIG_PTE_64BIT=y CONFIG_PHYS_64BIT=y CONFIG_PPC_MMU_NOHASH=y CONFIG_PPC_MMU_NOHASH_32=y CONFIG_NOT_COHERENT_CACHE=y CONFIG_PPC32=y CONFIG_WORD_SIZE=32 CONFIG_ARCH_PHYS_ADDR_T_64BIT=y CONFIG_MMU=y CONFIG_GENERIC_CMOS_UPDATE=y CONFIG_GENERIC_TIME_VSYSCALL=y CONFIG_GENERIC_CLOCKEVENTS=y CONFIG_GENERIC_HARDIRQS=y CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y CONFIG_IRQ_PER_CPU=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_GENERIC_HWEIGHT=y CONFIG_GENERIC_FIND_NEXT_BIT=y CONFIG_PPC=y CONFIG_EARLY_PRINTK=y CONFIG_GENERIC_NVRAM=y CONFIG_SCHED_OMIT_FRAME_POINTER=y CONFIG_ARCH_MAY_HAVE_PC_FDC=y CONFIG_PPC_OF=y CONFIG_PPC_UDBG_16550=y CONFIG_AUDIT_ARCH=y CONFIG_GENERIC_BUG=y CONFIG_ARCH_HIBERNATION_POSSIBLE=y CONFIG_PPC_DCR_NATIVE=y CONFIG_PPC_DCR=y CONFIG_ARCH_SUPPORTS_DEBUG_PAGEALLOC=y CONFIG_PPC_ADV_DEBUG_REGS=y CONFIG_PPC_ADV_DEBUG_IACS=4 CONFIG_PPC_ADV_DEBUG_DACS=2 CONFIG_PPC_ADV_DEBUG_DVCS=2 CONFIG_PPC_ADV_DEBUG_DAC_RANGE=y CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config" CONFIG_CONSTRUCTORS=y # # General setup # CONFIG_EXPERIMENTAL=y CONFIG_BROKEN_ON_SMP=y CONFIG_INIT_ENV_ARG_LIMIT=32 CONFIG_CROSS_COMPILE="" CONFIG_LOCALVERSION="" CONFIG_LOCALVERSION_AUTO=y CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_SYSVIPC_SYSCTL=y CONFIG_POSIX_MQUEUE=y CONFIG_POSIX_MQUEUE_SYSCTL=y # # RCU Subsystem # CONFIG_TREE_RCU=y CONFIG_RCU_FANOUT=32 CONFIG_LOG_BUF_SHIFT=14 CONFIG_BLK_DEV_INITRD=y CONFIG_INITRAMFS_SOURCE="" CONFIG_RD_GZIP=y CONFIG_SYSCTL=y CONFIG_ANON_INODES=y CONFIG_EMBEDDED=y CONFIG_SYSCTL_SYSCALL=y CONFIG_KALLSYMS=y CONFIG_HOTPLUG=y CONFIG_PRINTK=y CONFIG_BUG=y CONFIG_ELF_CORE=y CONFIG_BASE_FULL=y CONFIG_FUTEX=y CONFIG_EPOLL=y CONFIG_SIGNALFD=y CONFIG_TIMERFD=y CONFIG_EVENTFD=y CONFIG_SHMEM=y CONFIG_AIO=y CONFIG_HAVE_PERF_EVENTS=y # # Kernel Performance Events And Counters # CONFIG_VM_EVENT_COUNTERS=y CONFIG_PCI_QUIRKS=y CONFIG_SLUB=y CONFIG_HAVE_OPROFILE=y CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS=y CONFIG_HAVE_IOREMAP_PROT=y CONFIG_HAVE_KPROBES=y CONFIG_HAVE_KRETPROBES=y CONFIG_HAVE_ARCH_TRACEHOOK=y CONFIG_HAVE_DMA_ATTRS=y CONFIG_HAVE_REGS_AND_STACK_ACCESS_API=y CONFIG_HAVE_DMA_API_DEBUG=y # # IO Schedulers # CONFIG_IOSCHED_NOOP=y CONFIG_IOSCHED_DEADLINE=y CONFIG_IOSCHED_CFQ=y CONFIG_DEFAULT_CFQ=y CONFIG_DEFAULT_IOSCHED="cfq" CONFIG_INLINE_SPIN_UNLOCK=y CONFIG_INLINE_SPIN_UNLOCK_IRQ=y CONFIG_INLINE_READ_UNLOCK=y CONFIG_INLINE_READ_UNLOCK_IRQ=y CONFIG_INLINE_WRITE_UNLOCK=y CONFIG_INLINE_WRITE_UNLOCK_IRQ=y CONFIG_PPC4xx_PCI_EXPRESS=y # # Platform support # CONFIG_ARCHES=y CONFIG_CANYONLANDS=y CONFIG_BLUESTONE=y CONFIG_GLACIER=y CONFIG_REDWOOD=y CONFIG_EIGER=y CONFIG_PPC44x_SIMPLE=y CONFIG_460EX=y # # Kernel options # CONFIG_TICK_ONESHOT=y CONFIG_NO_HZ=y CONFIG_HIGH_RES_TIMERS=y CONFIG_GENERIC_CLOCKEVENTS_BUILD=y CONFIG_HZ_250=y CONFIG_HZ=250 CONFIG_SCHED_HRTICK=y CONFIG_PREEMPT_NONE=y CONFIG_BINFMT_ELF=y CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y CONFIG_ARCH_HAS_WALK_MEMORY=y CONFIG_ARCH_ENABLE_MEMORY_HOTREMOVE=y CONFIG_SPARSE_IRQ=y CONFIG_MAX_ACTIVE_REGIONS=32 CONFIG_ARCH_FLATMEM_ENABLE=y CONFIG_ARCH_POPULATES_NODE_MAP=y CONFIG_SELECT_MEMORY_MODEL=y CONFIG_FLATMEM_MANUAL=y CONFIG_FLATMEM=y CONFIG_FLAT_NODE_MEM_MAP=y CONFIG_HAVE_MEMBLOCK=y CONFIG_PAGEFLAGS_EXTENDED=y CONFIG_SPLIT_PTLOCK_CPUS=4 CONFIG_MIGRATION=y CONFIG_PHYS_ADDR_T_64BIT=y CONFIG_ZONE_DMA_FLAG=1 CONFIG_BOUNCE=y CONFIG_VIRT_TO_BUS=y CONFIG_DEFAULT_MMAP_MIN_ADDR=4096 CONFIG_STDBINUTILS=y CONFIG_PPC_4K_PAGES=y CONFIG_FORCE_MAX_ZONEORDER=11 CONFIG_CMDLINE_BOOL=y CONFIG_CMDLINE="" CONFIG_EXTRA_TARGETS="" CONFIG_SECCOMP=y CONFIG_ISA_DMA_API=y # # Bus options # CONFIG_ZONE_DMA=y CONFIG_NEED_DMA_MAP_STATE=y CONFIG_NEED_SG_DMA_LENGTH=y CONFIG_GENERIC_ISA_DMA=y CONFIG_PPC_INDIRECT_PCI=y CONFIG_4xx_SOC=y CONFIG_PPC_PCI_CHOICE=y CONFIG_PCI=y CONFIG_PCI_DOMAINS=y CONFIG_PCI_SYSCALL=y CONFIG_ARCH_SUPPORTS_MSI=y # # Advanced setup # # CONFIG_ADVANCED_OPTIONS is not set # # Default settings for advanced configuration options are used # CONFIG_LOWMEM_SIZE=0x3000 CONFIG_PAGE_OFFSET=0xc000 CONFIG_KERNEL_START=0xc000 CONFIG_PHYSICAL_START=0x CONFIG_TASK_SIZE=0xc000 CONFIG_CONSISTENT_SIZE=0x0020 CONFIG_NET=y # # Networking options # CONFIG_PACKET=y CONFIG_UNIX=y CONFIG_INET=y CONFIG_IP_FIB_HASH=y CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y CONFIG_IP_PNP_BOOTP=y CONFIG_INET_DIAG=y CONFIG_INET_TCP_DIAG=y CONFIG_TCP_CONG_CUBIC=y
RE: Combining defconfigs for 44x based boards
> > On Wed, Sep 08, 2010 at 03:40:37PM -0700, Tirumala Marri wrote: > > Is anyone working on Linus suggestion to combine the defconfigs under > 44x > > or 4xx ? > > Do you mean ppc44x_defconfig? Already there. No it is not there yet. I should have said "Linus suggestion about defconfigs in ARM mailing list". ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
RE: Combining defconfigs for 44x based boards
> > Linus made a suggestion to that effect? If so, I missed it. Have a > pointer? There was discussion going on in arm-kernel mailing list. And I see some patches being submitted for ARM based boards. I think we can also combine some of the defconfigs under arch/powerpc/configs/44x/ directory. Here is ARM dfconfigs discussion http://lkml.indiana.edu/hypermail/linux/kernel/1006.0/01464.html Here is the link for some of the defconfig submissions http://www.spinics.net/lists/arm-kernel/msg96972.html ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: Combining defconfigs for 44x based boards
Hi Marri, On Wed, 8 Sep 2010 15:39:29 -0700 Tirumala Marri wrote: > > Is anyone working on Linus suggestion to combine the defconfigs under 44x > or 4xx ? Are arch/powerpc/configs/ppc44x_defconfig and ppc40x_defconfig what you want? Or do you mean the Kconfig based versions? -- Cheers, Stephen Rothwells...@canb.auug.org.au http://www.canb.auug.org.au/~sfr/ pgpBSZLlepSCW.pgp Description: PGP signature ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: Combining defconfigs for 44x based boards
On Wed, Sep 08, 2010 at 03:40:37PM -0700, Tirumala Marri wrote: > Is anyone working on Linus suggestion to combine the defconfigs under 44x > or 4xx ? Do you mean ppc44x_defconfig? Already there. -Olof ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Re: Combining defconfigs for 44x based boards
On Wed, Sep 08, 2010 at 03:40:37PM -0700, Tirumala Marri wrote: >Is anyone working on Linus suggestion to combine the defconfigs under 44x >or 4xx ? Linus made a suggestion to that effect? If so, I missed it. Have a pointer? josh ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Combining defconfigs for 44x based boards
Is anyone working on combining defconfigs for 44x or 4xx devices ? Regards, Marri ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
Combining defconfigs for 44x based boards
Is anyone working on Linus suggestion to combine the defconfigs under 44x or 4xx ? Thanks, Marri ___ Linuxppc-dev mailing list Linuxppc-dev@lists.ozlabs.org https://lists.ozlabs.org/listinfo/linuxppc-dev
