From: Ivan Kuten <ivan.kuten@promwad.com>
To: buildroot@busybox.net
Subject: [Buildroot] Undefined instruction on PXA270
Date: Thu, 22 Nov 2007 11:03:31 +0200 [thread overview]
Message-ID: <474545E3.9090109@promwad.com> (raw)
In-Reply-To: <20071121233524.GB11890@buzzloop.caiaq.de>
Hi,
I'd suggest trying to build compatible toolchain for ARM, armv4 for example 920T
and build kernel separately with other good toolchain.
And next to compare by objdump generated code by armv4 and xscale toolchain.
Post your gcc --dumpspecs
Daniel Mack wrote:
> Hi,
>
> we've been trying to hunt a bug of our buildroot based rootfs here
> without success. The platform is based on a PXA270 (Compulab's EM-X270)
> and buildroot is a recent svn checkout.
>
> The buildroot config is attached. Any ideas where to dig?
>
> Thanks and best regards,
> Daniel
>
Regards,
Ivan
--
--------------------------------
Embedded Linux engineer,
Promwad Company: http://www.promwad.com/
Homepage : http://www.ivankuten.com/
--------------------------------
next prev parent reply other threads:[~2007-11-22 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-21 23:35 [Buildroot] Undefined instruction on PXA270 Daniel Mack
2007-11-22 9:03 ` Ivan Kuten [this message]
2007-11-22 10:15 ` ing. Federico Fuga
2007-12-02 22:31 ` Daniel Mack
2007-12-04 18:53 ` ing. Federico Fuga
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=474545E3.9090109@promwad.com \
--to=ivan.kuten@promwad.com \
--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