On Thu, Oct 08, 2015 at 02:56:36AM -0700, Tony Lindgren wrote: > * Russell King - ARM Linux <linux@xxxxxxxxxxxxxxxx> [151008 02:40]: > > On Thu, Oct 08, 2015 at 01:40:21AM -0700, Tony Lindgren wrote: > > > Well the way distros deal with issues like this is have everything > > > possible as loadable modules. We should get the regulator_pbiaa > > > loaded automatically in that case as long as it's in the dts.. And > > > as long as we have the MODULE_DEVICE_TABLE entries right. > > > > Assuming you have a rootfs which doesn't depend on one of those modules, > > or an initramfs, and a way to get the built modules into that initial > > filesystem. Automated test boot systems do not have that luxury: the > > generation of initramfs is distro specific, and would be very large if > > it were to include all possible modules. > > Right, we need to keep the kernel usable in all these configurations > somehow. > > For the kernel generated minimal initramfs we could grep for the > needed modules in the dts file. Yes, you might be able to do that, but the only thing that can generate the initramfs is the target system itself, or a similar target system. For example, you can't sanely generate an initramfs for an ARM Ubuntu system on an x86 Fedora host. Distros have the luxury of always being able to do the initramfs generation on the target system at installation or distro kernel update time. -- FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net. -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
