Sorry for the shameless ping, but I'd really like to know the way forward here... -----Original Message----- From: "Joe Woodward" <jw@xxxxxxxxxxxxxx> To: "Shilimkar, Santosh" <santosh.shilimkar@xxxxxx>, "Catalin Marinas" <catalin.marinas@xxxxxxx> Cc: "Aneesh V" <aneesh@xxxxxx>, "Russell King - ARM Linux" <linux@xxxxxxxxxxxxxxxx>, linux-omap@xxxxxxxxxxxxxxx, "linux-arm" <linux-arm- kernel@xxxxxxxxxxxxxxxxxxx> Date: Fri, 20 Jan 2012 08:57:11 +0000 Subject: Re: OMAP3 L2/outer cache enabled in kernel (after being disabled by uBoot)? > > > > So I re-iterate that we need to have solution to this problem. > > > > ... I don't want to be a pain, but it seems to me that this dicussion > didn't reach a full conclussion? > > I think it was left with the open options being: > 1) Leave the L2/outer cache enabled in the bootloader (not ideal and > may cause problems with future devices) > 2) Turn the L2/outer cache on for OMAP3 later in the kernel boot when > the device is known > > Is there any concensus? > > Cheers, > Joe > > > Regards > > Santosh > > > -- > 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 -- 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
