Hi, On Fri, Dec 26, 2014 at 02:08:10PM +0200, Igor Grinberg wrote: > >> I think we should move omap2plus_defconfig to be mostly modular and > >> usable for distros as a base. Most distros prefer to build almost > >> everything as loadable modules. And my preference is that we should > >> only keep the minimum rootfs for devices and serial support as > >> built-in and rely on initramfs for most drivers. And slowly move > >> also the remaining built-in drivers to be loadable modules. > >> > >> The reasons for having drivers as loadable modules are many. It > >> allows distros to use the same kernel for all the devices without > >> bloating the kernel. It makes developing drivers easier as just the > >> module needs to be reloaded. And loadable modules protect us from > >> cross-framework spaghetti calls in the kernel as the interfaces are > >> clearly defined. > >> > >> Are there people really using SATA as rootfs right now on omaps? > > > > not that we know :-) The only platforms available today with SATA are > > OMAP5432 uEVM and DRA7x EVM, > > I'm sorry... that is not true. That's not what you have said thus far. So far you only said it *can* have, you have not explicitly said a customer really *is* using rootfs on SATA. Personally, I really don't care. It's just a defconfig patch and kernel configuration is very, very easy to change at any time. You can even have an out of tree config fragment just turning SATA=y again. Have a look at scripts/kconfig/merge_config.sh > > the latter being mostly used by TIers as of > > now (at least from mainline point of view). > > the keyword is mostly... And I'm also not sure this is true these days... > > But, really, don't mind me. We will find our solutions (we always did). > I mean, Felipe wants it out so badly... > Who am I to say anything... cute :-) -- balbi
Attachment:
signature.asc
Description: Digital signature
