Re: Making ARM multiplatform kernels DT-only?
|[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
On Thursday 03 May 2012, Russell King - ARM Linux wrote: > On Thu, May 03, 2012 at 01:50:35PM +0000, Arnd Bergmann wrote: > > My feeling is that we should just mandate DT booting for multiplatform > > kernels, because it significantly reduces the combinatorial space > > at compile time, avoids a lot of legacy board files that we cannot > > test anyway, reduces the total kernel size and gives an incentive > > for people to move forward to DT with their existing boards. > > On this point, I strongly object, especially as I'm one who uses the > existing non-DT multiplatform support extensively. It's really not > a problem for what you're trying to achieve. Just to clarify the terminology, when I said "multiplatform", I did not mean enabling more than one board file inside a given mach-* directory but instead enabling multiple mach-* directories that are currently mutually exclusive, i.e. the future stuff you replied to in the other mail, not what everyone is doing today, and this would not stop anything from working that works today. > I think what you're proposing is a totally artificial restriction. > There's no problem with a kernel supporting DT and non-DT together. > We've proven that many many times. I prove it every night that my > build and boot system runs - the OMAP LDP boots a multiplatform kernel > just fine without DT. Of course it's an artificial restriction, if it was a technical necessity, I would not have needed to ask ;-) IMHO however it's a helpful restriction. My current count of board files is 393 and if you consider that we won't build v6+ and v4/v5 together and that some of them will probably not be multiplatform capable for a long time, we probably end up with about half of them in a given kernel, which is still a lot and I would not expect distributors to make a good decision about which ones of these are important to enable and which ones are not. If we restrict the Kconfig space to just the ones that are DT-enabled, we can be reasonably sure that these have been recently tested on actual hardware by someone who cares about them, and we get only a fraction of the user visible options, roughly one per soc generation. One counterargument that just occurred to me is build coverage, and it would be nice to have "make allyesconfig" actually build everything together as far as possible. We could get a bit closer to that if we allow those platforms that have no DT support to just provide a Kconfig option for multiplatform kernels that enables everything, e.g. when you build an ARMv4/ARMv5 kernel, you can enable all sa1100 based boards together using one option, but when you build an sa1100 kernel, you keep picking them individually. Arnd -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
[Other Archives] [Linux Kernel Newbies] [Linux Driver Development] [Fedora Kernel] [Linux Kernel Testers] [Linux SH] [Linux Omap] [Linux Kbuild] [Linux Tape] [Linux Input] [Linux Kernel Janitors] [Linux Kernel Packagers] [Linux Doc] [Linux Man Pages] [Linux API] [Linux Memory Management] [Linux Modules] [Linux Standards] [Kernel Announce] [Netdev] [Git] [Linux PCI] Linux CAN Development [Linux I2C] [Linux RDMA] [Linux NUMA] [Netfilter] [Netfilter Devel] [SELinux] [Bugtraq] [FIO] [Linux Perf Users] [Linux Serial] [Linux PPP] [Linux ISDN] [Linux Next] [Kernel Stable Commits] [Linux Tip Commits] [Kernel MM Commits] [Linux Security Module] [AutoFS] [Filesystem Development] [Ext3 Filesystem] [Linux bcache] [Ext4 Filesystem] [Linux BTRFS] [Linux CEPH Filesystem] [Linux XFS] [XFS] [Linux NFS] [Linux CIFS] [Ecryptfs] [Linux NILFS] [Linux Cachefs] [Reiser FS] [Initramfs] [Linux FB Devel] [Linux OpenGL] [DRI Devel] [Fastboot] [Linux RT Users] [Linux RT Stable] [eCos] [Corosync] [Linux Clusters] [LVS Devel] [Hot Plug] [Linux Virtualization] [KVM] [KVM PPC] [KVM ia64] [Linux Containers] [Linux Hexagon] [Linux Cgroups] [Util Linux] [Wireless] [Linux Bluetooth] [Bluez Devel] [Ethernet Bridging] [Embedded Linux] [Barebox] [Linux MMC] [Linux IIO] [Sparse] [Smatch] [Linux Arch] [x86 Platform Driver] [Linux ACPI] [Linux IBM ACPI] [LM Sensors] [CPU Freq] [Linux Power Management] [Linmodems] [Linux DCCP] [Linux SCTP] [ALSA Devel] [Linux USB] [Linux PA RISC] [Linux Samsung SOC] [MIPS Linux] [IBM S/390 Linux] [ARM Linux] [ARM Kernel] [ARM MSM] [Tegra Devel] [Sparc Linux] [Linux Security] [Linux Sound] [Linux Media] [Video 4 Linux] [Linux IRDA Users] [Linux for the blind] [Linux RAID] [Linux ATA RAID] [Device Mapper] [Linux SCSI] [SCSI Target Devel] [Linux SCSI Target Infrastructure] [Linux IDE] [Linux SMP] [Linux AXP] [Linux Alpha] [Linux M68K] [Linux ia64] [Linux 8086] [Linux x86_64] [Linux Config] [Linux Apps] [Linux MSDOS] [Linux X.25] [Linux Crypto] [DM Crypt] [Linux Trace Users] [Linux Btrace] [Linux Watchdog] [Utrace Devel] [Linux C Programming] [Linux Assembly] [Dash] [DWARVES] [Hail Devel] [Linux Kernel Debugger] [Linux gcc] [Gcc Help] [X.Org] [Wine]
[Older Kernel Discussion] [Yosemite National Park Forum] [Large Format Photos] [Gimp] [Yosemite Photos] [Stuff]