From: Andrew Dyer <amdyer@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: MIPS LE build problems
Date: Tue, 9 Aug 2005 18:23:59 -0500 [thread overview]
Message-ID: <c166aa9f0508091623642cef58@mail.gmail.com> (raw)
In-Reply-To: <42F92903.8040306@corelatus.se>
On 8/9/05, Thomas Lange <thomas@corelatus.se> wrote:
> It seems that Wolfgangs original message got lost somewhere.
>
> I have attached the patch.
>
> /Thomas
I think the board linker scripts also need to be modified to
work with either big or little endian toolchains like below. The third
argument to OUTPUT_FORMAT is only used for explicitly little endian
compilation.
--- /home/adyer/Projects/u-boot/board/dbau1x00/u-boot.lds
2005-07-25 20:11:54.000000000 -0500
+++ u-boot.lds 2005-07-10 18:17:44.000000000 -0500
@@ -22,9 +22,9 @@
*/
/*
-OUTPUT_FORMAT("elf32-bigmips", "elf32-bigmips", "elf32-bigmips")
+OUTPUT_FORMAT("elf32-bigmips", "elf32-bigmips", "elf32-littlemips")
*/
-OUTPUT_FORMAT("elf32-tradbigmips", "elf32-tradbigmips", "elf32-tradbigmips")
+OUTPUT_FORMAT("elf32-tradbigmips", "elf32-tradbigmips", "elf32-tradlittlemips")
OUTPUT_ARCH(mips)
ENTRY(_start)
SECTIONS
The test that decides which endianess to build is not going to work for
toolchains other than Denx ones, lots of them have prefixes that don't
include 4KCle (they may not build u-boot very well, but that's another issue)
I would suggest doing it by config name and putting ENDIANNESS in
config.mk something like so (untested):
dbau1550_config \
dbau1550_el_config : unconfig
@ >include/config.h
@[ -z "$(findstring _el,$@)" ] || \
{ echo "ENDIANNESS = little" >>include/config.mk ; \
echo "little endian" ; \
}
@echo "#define CONFIG_DBAU1550 1" >>include/config.h
@./mkconfig -a dbau1x00 mips mips dbau1x00
and test for endianness in cpu/mips/config.mk and do the right thing.
--
Hardware, n.:
The parts of a computer system that can be kicked.
next prev parent reply other threads:[~2005-08-09 23:23 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 21:13 [U-Boot-Users] MIPS LE build problems Wolfgang Denk
2005-08-09 16:59 ` [U-Boot-Users] " Thomas Lange
2005-08-09 19:47 ` Matej Kupljen
2005-08-09 20:56 ` Thomas Lange
2005-08-09 22:06 ` Thomas Lange
2005-08-09 23:23 ` Andrew Dyer [this message]
2005-08-10 6:06 ` Matej Kupljen
2005-08-10 6:52 ` Wolfgang Denk
2005-08-10 7:01 ` Matej Kupljen
2005-08-10 7:32 ` Wolfgang Denk
2005-08-10 7:43 ` Matej Kupljen
2005-08-10 8:45 ` Wolfgang Denk
2005-08-10 9:13 ` Matej Kupljen
2005-08-10 10:18 ` Wolfgang Denk
2005-08-17 7:07 ` Matej Kupljen
2005-08-17 8:08 ` Wolfgang Denk
2005-08-17 8:24 ` Matej Kupljen
2005-08-17 13:44 ` Wolfgang Denk
2005-08-18 6:31 ` Matej Kupljen
2005-08-18 8:46 ` Wolfgang Denk
2005-08-18 9:01 ` Matej Kupljen
2005-08-18 8:42 ` Matej Kupljen
2005-08-18 8:51 ` Wolfgang Denk
2005-08-18 9:08 ` Matej Kupljen
2005-08-18 19:54 ` Udi Finkelstein
2005-08-18 20:56 ` Wolfgang Denk
2005-08-19 8:59 ` Udi Finkelstein
2005-08-18 20:46 ` Wolfgang Denk
2005-08-19 4:55 ` Matej Kupljen
2005-08-18 18:31 ` Jerry Van Baren
2005-08-10 6:05 ` Matej Kupljen
2006-07-22 18:47 ` [U-Boot-Users] " Wolfgang Denk
-- strict thread matches above, loose matches on Subject: below --
2005-08-18 21:38 [U-Boot-Users] " Wolfgang Denk
2005-08-18 23:11 ` Zachary Landau
2005-08-18 23:28 ` Wolfgang Denk
2005-08-20 7:51 ` Matej Kupljen
2005-08-22 8:53 ` Leif Lindholm
2005-08-22 8:59 ` Wolfgang Denk
2005-08-24 8:54 ` Matej Kupljen
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=c166aa9f0508091623642cef58@mail.gmail.com \
--to=amdyer@gmail.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