* Jarkko Nikula <jhnikula@xxxxxxxxx> [100602 17:06]: > On Wed, 2 Jun 2010 16:57:10 +0300 > Tony Lindgren <tony@xxxxxxxxxxx> wrote: > > > > Problem is that amount of expansion boards is practically unlimited so > > > patching bootloader and board file could come quite maintenance effort. > > > > > > Of course there are some lets say generic boards but bunch of in-house, > > > DIY, etc. boards and there is no point to patch common bootloader and > > > kernel board files because of them. > > > > Just saveenv the kernel cmdline options in u-boot? > > > I meant that if kernel module could do muxing then there is no need the > user to change muxings for different add-on boards. > > Works fine if you have one board but how about when amount of expansion > boards grow? Yeah having the modules do the platform device init and registration will lead into nasty conflicts. The platform device registration really needs to happen in the board-*.c files, not in the drivers. Tony -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
