From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [ARM] one warning left for all ARM boards
Date: Tue, 10 Jul 2012 01:37:46 -0700 [thread overview]
Message-ID: <20120710083746.GA5053@oliver-linux> (raw)
In-Reply-To: <201207100353.43631.marex@denx.de>
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 <trini@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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20120710/fa9595b6/attachment.pgp>
next prev parent reply other threads:[~2012-07-10 8:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 15:42 [U-Boot] [ARM] one warning left for all ARM boards Albert ARIBAUD
2012-07-09 19:48 ` Wolfgang Denk
2012-07-09 20:42 ` Tom Rini
2012-07-09 20:47 ` Albert ARIBAUD
2012-07-09 21:07 ` Tom Rini
2012-07-09 21:53 ` Albert ARIBAUD
2012-07-10 1:53 ` Marek Vasut
2012-07-10 8:37 ` Tom Rini [this message]
2012-07-10 8:46 ` Ilya Yanok
2012-07-10 8:52 ` Tom Rini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120710083746.GA5053@oliver-linux \
--to=trini@ti.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.