From: Dan Malek <dan@embeddedalley.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] U-Boot on ARMEB
Date: Wed, 18 Jan 2006 16:29:12 -0500 [thread overview]
Message-ID: <df78ded71cfd994db17cab8d4da70627@embeddedalley.com> (raw)
In-Reply-To: <43CEAD65.6070609@precidia.com>
On Jan 18, 2006, at 4:04 PM, Brian White wrote:
> That's what I'm figuring out, but it tried to create a link from
> "asm-arm" and I wasn't sure if there were endian dependencies there.
> Can I just link it to "asm-armeb" and have it work?
All I did was build some cross tools, called them armeb-gcc, etc.
Then:
setenv ARCH arm
setenv CROSS_COMPILE armeb-
make ixdp425_config
make
and ended up with a big endian U-Boot. I started hacking from
there and haven't seen any problems. If there are any, we have
not found them yet.
> I think I'm just going to link all my tools so they're available as
> both "armeb-linux" and "arm-linux". My worry is that something will
> be specifically little-endian somewhere and will be quietly compiled
> incorrectly.
I think you worry too much, and naming the same tool by those two
different
names would seem to be more of a problem than doing it properly.
If the tools are built correctly for big endian ARM, it seems everything
works fine.
I have no further comments on the subject. Good Luck. :-)
-- Dan
next prev parent reply other threads:[~2006-01-18 21:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 19:30 [U-Boot-Users] U-Boot on ARMEB Brian White
2006-01-18 19:43 ` Dan Malek
2006-01-18 21:04 ` Brian White
2006-01-18 21:29 ` Dan Malek [this message]
2006-01-19 0:49 ` Brian White
2006-01-19 12:31 ` Stefan Roese
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=df78ded71cfd994db17cab8d4da70627@embeddedalley.com \
--to=dan@embeddedalley.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