From: Jeff Angielski <jeff@theptrgroup.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] cross compiling fw_printenv on big endian
Date: Tue, 16 Mar 2010 15:17:02 -0400 [thread overview]
Message-ID: <4B9FD92E.7000400@theptrgroup.com> (raw)
I seem to be having a problem with fw_printenv on my PowerPC 85xx target
whereby I constantly get CRC32 errors:
# fw_printenv
Warning: Bad CRC, using default environment
I tracked this down to the fact that u-boot/lib_generic/crc32.c is
getting compiled with the __LITTLE_ENDIAN defined even though I have
CROSS_COMPILE setup correctly [e.g. I can build u-boot.bin just fine].
Is there a special way to cross compile fw_printenv so that the
__LITTLE_ENDIAN is not defined? Are there other PowerPC users that are
building fw_printenv?
I'd rather do the "proper" thing than resort of hacking the crc32.c file.
--
Jeff Angielski
The PTR Group
www.theptrgroup.com
next reply other threads:[~2010-03-16 19:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 19:17 Jeff Angielski [this message]
2010-03-17 10:34 ` [U-Boot] cross compiling fw_printenv on big endian Detlev Zundel
2010-03-17 10:47 ` Joakim Tjernlund
2010-03-17 11:57 ` Wolfgang Denk
2010-03-17 14:22 ` Joakim Tjernlund
2010-03-17 15:10 ` Jeff Angielski
2010-03-17 17:09 ` Joakim Tjernlund
2010-03-17 19:18 ` Jeff Angielski
2010-03-21 19:29 ` Wolfgang Denk
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=4B9FD92E.7000400@theptrgroup.com \
--to=jeff@theptrgroup.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.