On Fri, Mar 16, 2012 at 12:48 AM, Sricharan R <r.sricha...@ti.com> wrote: > Tom, > <snip..> > >> > > > Is an #error in a common omap4/5 file sufficient or does it need >> to be >> > > > sooner than that? >> > > >> > > If it can be tested there, it can probably also tested before we >> start >> > > building at all? >> > >> > I suspect no just because the kernel does this in >> > <linux/compiler-gcc[45].h> >> >> I take it back, we can do that if we bring in the archprepare rule >> logic >> that the kernel has. I'll go down this path now... >> > Today though out of 40KB of non secure SRAM on OMAP4 > we cannot use more than 32KB of SRAM in EMU devices > because of romcode restrictions.
Ah, I forgot about the romcode. But other devices allow for more yes (since the currently enforced limit is 38kB) ? > OMAP5 is not a problem where we have sufficient > Non SECURE SRAM. > > Just to understand, are we now required to > introduce #error macro in OMAP4 to get this through ? No, I just need to post the patches I have that introduce a gcc version check prior to building. It's lifted in part from the kernel, but our Makefiles are too different for the kernel way to just work :( -- Tom _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot