On Tue, Jan 31, 2012 at 09:53:25AM +0000, Catalin Marinas wrote: > Maybe we could factor out the CPU-specific settings from proc-v*.S > into a separate arch/arm/boot/preload directory. We keep proc-v*.S > entirely generic and the implementation-defined bits setting in the > preload code. You could have an option to link the preload with the > kernel but we could recommend that people run this code from > boot-loader before invoking the kernel. You've seen the resistance from uboot to stuff we do with the kernel, this will be no different. There's also quite a number of boot loaders out there which aren't capable of running a binary, returning and then loading and running the kernel. Plus, of course, it's far from friendly towards TFTP setups. -- 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
