From: Marcel <korgull@home.nl>
To: buildroot@busybox.net
Subject: [Buildroot] endian issue
Date: Sat, 15 May 2010 17:18:44 +0200 [thread overview]
Message-ID: <201005151718.44917.korgull@home.nl> (raw)
In-Reply-To: <1273933182.28330.87.camel@coalu.atr>
On Saturday 15 May 2010 04:19:42 pm Lionel Landwerlin wrote:
> The endianness configuration of your processor isn't something you can
> usually change 'on-the-fly'. It's usually set up early in the boot
> process.
> So you have to choose whether you want to compile all your system in big
> or little endian, you can select that from the buildroot architecture
> configuration (arm -> little, armeb -> big, for example).
That's clear.
My board is being developed from an environment I got from in-circuit.
arm is selected (not armeb) and indeed the packages are compiled in little
endian format.
Are there any additional items I should be aware of when switching from arm to
armeb ?
> > Is there any way to compile my package in big-endian mode from buildroot
> > ? Or is there another way I should force this ?
>
> You can't select that for 1 package, it's for the whole system or
> nothing.
> Otherwise, the smartest approch would be to make endian detection (at
> compile time or at running time) to adapt your processing algorithm.
Well, the biggest issue I have is that my data that gets send out to the host
PC must be in big-endian format. My drivers work this way too so the best
would be if everything is big-endian so that I can transfer data from my
drivers, through the package to the host PC without touching the data.
I could leave everything in little endian format but I would than have to
reformat my data before sending it out. Although this is not all that difficult
I don't like to waste time in that process.
Thanks for your reply,
Marcel
prev parent reply other threads:[~2010-05-15 15:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-15 13:47 [Buildroot] endian issue Marcel
2010-05-15 14:09 ` Grant Edwards
2010-05-15 14:19 ` Lionel Landwerlin
2010-05-15 14:43 ` Grant Edwards
2010-05-15 15:26 ` Marcel
2010-05-15 16:33 ` Thomas Petazzoni
2010-05-15 16:37 ` Lionel Landwerlin
2010-05-15 16:45 ` Grant Edwards
2010-05-15 17:53 ` Marcel
2010-05-15 15:18 ` Marcel [this message]
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=201005151718.44917.korgull@home.nl \
--to=korgull@home.nl \
--cc=buildroot@busybox.net \
/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