From mboxrd@z Thu Jan 1 00:00:00 1970 From: linux@arm.linux.org.uk (Russell King - ARM Linux) Date: Tue, 31 Jan 2012 10:10:00 +0000 Subject: OMAP3 L2/outer cache enabled in kernel (after being disabled by uBoot)? In-Reply-To: References: <20120117133918.GE11475@arm.com> <20120127173029.GA3281@arm.com> <4F277A6E.9070107@ti.com> Message-ID: <20120131101000.GA1275@n2100.arm.linux.org.uk> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org 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.