On Tue, Jul 10, 2012 at 03:53:43AM +0200, Marek Vasut wrote: > Dear Albert ARIBAUD, > > > Hi Tom, > > > > On Mon, 9 Jul 2012 14:07:22 -0700, Tom Rini <tr...@ti.com> wrote: > > > On Mon, Jul 09, 2012 at 09:48:18PM +0200, Wolfgang Denk wrote: > > > > Dear Albert ARIBAUD, > > > > > > > > In message <20120709174210.0bc0cef5@aari01-12> you wrote: > > > > > With the latest commits on u-boot/master, two obnoxious "attention" > > > > > messages were removed from ARM builds, but one still remains: > > > > > > > > > > attention : -fstack-usage not supported for this target [enabled by > > > > > default] > > > > > > > > As recommended on the ML I reverted the commit that caused this > > > > trouble, waiting to see a new (more carefully tested) version to be > > > > applied instead. > > > > > > > > At the moment ARM is build clean, as far as I can tell. > > > > > > > > If nobody adds any new pull requests very soon now, I'll go for -rc1. > > > > > > What do we want to do about the USB issue (on ARM platforms, with EHCI, > > > with >32byte alignment requirements, if dcache isn't build-time > > > disabled, USB is unusable, a change from previous releases), for this > > > release? Are we going to hope the alignment issues can be flushed out > > > and fixed well enough before the final release? Should we go with > > > disable the dcache now, continue working on it for the next? > > > > What are the chances that the issue be fixed? > > Low ... this is some deep crap that's growing through uboot as whole :-( And > it's not only USB.
Then I propose 1, 3, 4, 5, 6 from my v4 series (remove dcache_off call from ehci-omap.c as it's wrong, build-time disable DCACHE on USB enabling platforms). Yes, we're papering over bugs for a release, but we (a) know we're doing it and (b) are trying to fix them and (c) can't fix them in time. -- Tom
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
