From: Daniel Schwierzeck <daniel.schwierzeck@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] MIPS: fix endianess handling
Date: Mon, 05 Dec 2011 01:04:41 +0100 [thread overview]
Message-ID: <4EDC0A99.6090106@googlemail.com> (raw)
In-Reply-To: <20111204150618.CBCA925EA22@gemini.denx.de>
On 12/04/2011 04:06 PM, Wolfgang Denk wrote:
> Dear Daniel Schwierzeck,
>
> In message<4EDB5F86.40605@googlemail.com> you wrote:
>>
>> Wolfgang, is there any reason why standalone apps are linked without
>> LDFLAGS (especially PLATFORM_LDFLAGS)?
>
> None that I know, at least.
>
> In general, standalone applications are a rarely used special feature,
> and the few people who actually ever used this for a purpose probably
> used custom code and custom linker scripts, so the mainline code is
> eventually not that good supproted.
the problem is those apps are always compiled. Maybe we should introduce
a config option to enable building only if someone really needs them?
>
>> This patch fixes a general issue with standalone apps on archs
>> supporting both endianess types when running MAKEALL. I guess this could
>> be relevant for ARM too if U-Boot has support for big-endian ARM boards.
>
> It does, but I doubt anybody ever used standalone applications on
> these.
>
> Best regards,
>
> Wolfgang Denk
>
--
Best regards,
Daniel
next prev parent reply other threads:[~2011-12-05 0:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 13:42 [U-Boot] [PATCH] MIPS: fix endianess handling Daniel Schwierzeck
[not found] ` <CACUy__XYf2Zo3d0SQ7Ub-ea37C2X=gZ+bTMTX95vz+YdAeQhDw@mail.gmail.com>
2011-12-04 14:32 ` Shinya Kuribayashi
2011-12-04 15:08 ` Wolfgang Denk
2011-12-05 0:10 ` Daniel Schwierzeck
2012-03-31 20:54 ` Marek Vasut
[not found] ` <4EDB5F86.40605@googlemail.com>
2011-12-04 15:06 ` Wolfgang Denk
2011-12-05 0:04 ` Daniel Schwierzeck [this message]
2011-12-05 10:05 ` Wolfgang Denk
2011-12-07 12:59 ` [U-Boot] [PATCH v2] " Daniel Schwierzeck
2011-12-11 16:53 ` [U-Boot] [PATCH v3] " Daniel Schwierzeck
2011-12-16 18:12 ` 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=4EDC0A99.6090106@googlemail.com \
--to=daniel.schwierzeck@googlemail.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.