From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v4 0/6] Enable Thumb build for ARM platforms
Date: Thu, 15 Mar 2012 15:21:18 -0700 [thread overview]
Message-ID: <20120315222118.GC6855@bill-the-cat> (raw)
In-Reply-To: <20120315211251.GB6855@bill-the-cat>
On Thu, Mar 15, 2012 at 02:12:51PM -0700, Tom Rini wrote:
> On Thu, Mar 15, 2012 at 10:01:50PM +0100, Wolfgang Denk wrote:
> > Dear Tom Rini,
> >
> > In message <CA+M6bXkBodKLkkqFseqo=BeNuL62W-MUSgsTEYgV4WLEvf1GtA@mail.gmail.com> you wrote:
> > >
> > > > I don't consider it a big problem (just a bit sad) if ELDK 4.2 cannot
> > > > be used for building these. However, I think it is not acceptable
> > > > tobuild known-to-be-broken images. If the tool chain is too old, this
> > > > shall result in a clear error message and abort of the build.
> > >
> > > 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...
--
Tom
next prev parent reply other threads:[~2012-03-15 22:21 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 17:20 [U-Boot] [PATCH v4 0/6] Enable Thumb build for ARM platforms Aneesh V
2012-03-08 17:20 ` [U-Boot] [PATCH v4 1/6] arm: adapt asm/linkage.h from Linux Aneesh V
2012-03-11 2:01 ` Mike Frysinger
2012-03-12 8:11 ` Aneesh V
2012-03-08 17:20 ` [U-Boot] [PATCH v4 2/6] armv7: add appropriate headers for assembly functions Aneesh V
2012-03-11 2:02 ` Mike Frysinger
2012-03-08 17:20 ` [U-Boot] [PATCH v4 3/6] ARM: enable Thumb build Aneesh V
2012-03-11 2:02 ` Mike Frysinger
2012-03-12 8:20 ` Aneesh V
2012-03-08 17:20 ` [U-Boot] [PATCH v4 4/6] armv7: Use -march=armv7-a and thereby enable Thumb-2 Aneesh V
2012-05-23 15:01 ` Thierry Reding
2012-05-23 15:20 ` Stephen Warren
2012-05-24 6:46 ` Thierry Reding
2012-07-06 23:02 ` Marek Vasut
2012-07-06 23:32 ` Tetsuyuki Kobayashi
2012-07-06 23:43 ` Aneesh V
2012-07-07 7:59 ` Marek Vasut
2012-07-07 10:08 ` Albert ARIBAUD
2012-03-08 17:20 ` [U-Boot] [PATCH v4 5/6] omap4+: Avoid using __attribute__ ((__packed__)) Aneesh V
2012-03-08 17:20 ` [U-Boot] [PATCH v4 6/6] OMAP4: enable Thumb build Aneesh V
2012-03-15 13:25 ` [U-Boot] [PATCH v4 0/6] Enable Thumb build for ARM platforms Aneesh V
2012-03-15 16:29 ` Tom Rini
2012-04-03 22:48 ` Allen Martin
2012-04-03 22:59 ` Måns Rullgård
2012-03-15 20:23 ` Tom Rini
2012-03-15 20:46 ` Wolfgang Denk
2012-03-15 20:54 ` Tom Rini
2012-03-15 21:01 ` Wolfgang Denk
2012-03-15 21:12 ` Tom Rini
2012-03-15 22:21 ` Tom Rini [this message]
2012-03-16 7:16 ` Wolfgang Denk
2012-03-16 7:48 ` Sricharan R
2012-03-16 14:36 ` Tom Rini
2012-03-17 7:10 ` R, Sricharan
2012-03-16 15:27 ` [U-Boot] [PATCH 1/2] tools, config.mk: Add gcc-version.sh, cc-version test from Linux Tom Rini
2012-03-16 15:27 ` [U-Boot] [PATCH 2/2] Makefile: Add a 'checkthumb' rule Tom Rini
2012-03-16 16:07 ` Mike Frysinger
2012-03-16 17:09 ` Tom Rini
2012-03-16 16:34 ` [U-Boot] [PATCH v2] " Tom Rini
2012-03-16 19:40 ` Mike Frysinger
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=20120315222118.GC6855@bill-the-cat \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox