public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Detlev Zundel <dzu@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] cross compiling fw_printenv on big endian
Date: Wed, 17 Mar 2010 11:34:19 +0100	[thread overview]
Message-ID: <m24okf44pg.fsf@ohwell.denx.de> (raw)
In-Reply-To: <4B9FD92E.7000400@theptrgroup.com> (Jeff Angielski's message of "Tue, 16 Mar 2010 15:17:02 -0400")

Hi Jeff,

> 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].

This makes little sense to me, as then the crc version used in U-Boot
would also use a wrong endianness.  Are you sure this happens?  Las time
I used the tool it worked for me without any such hacks.

Cheers
  Detlev

-- 
The limits of my language stand for the limits of my world.
                                        -- Ludwig Wittgenstein
--
DENX Software Engineering GmbH,      MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich,  Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-40 Fax: (+49)-8142-66989-80 Email: dzu at denx.de

  reply	other threads:[~2010-03-17 10:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-16 19:17 [U-Boot] cross compiling fw_printenv on big endian Jeff Angielski
2010-03-17 10:34 ` Detlev Zundel [this message]
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=m24okf44pg.fsf@ohwell.denx.de \
    --to=dzu@denx.de \
    --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