From: ing. Federico Fuga <fuga@studiofuga.com>
To: buildroot@busybox.net
Subject: [Buildroot] Undefined instruction on PXA270
Date: Thu, 22 Nov 2007 11:15:10 +0100 [thread overview]
Message-ID: <474556AE.8060209@studiofuga.com> (raw)
In-Reply-To: <20071121233524.GB11890@buzzloop.caiaq.de>
Daniel Mack ha scritto:
> 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.
>
> Out kernel 2.6.23 was successfully built with the toolchain set up by
> buildroot and can mount root filesystems provided by the vendor of the
> module. However, whenever trying to nfs-mount a rootfs built by BR2, we
> end up having messages like this:
>
Hi Daniel,
I am working on the same platform and board, emx270 from compulab, and
never found that problem. The only problem I had was with the
monotonic_syscall option you told, but never happened again.
I posted my configuration file back in this ml, search on the old posts
(a post titled "Illegal instruction on arm buildroot" or similar) and
start from that (just remember to check the monotonic_syscall
option/patch/similar).
If you don't find it, please write me in pvt so I can send you the file
without disturb the ml.
Please, if you solve the problem, tell me if you can make alsa-lib and
alsactl to work (I am experiencing some problem).
Best regards,
ing. Federico Fuga
next prev parent reply other threads:[~2007-11-22 10:15 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
2007-11-22 10:15 ` ing. Federico Fuga [this message]
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=474556AE.8060209@studiofuga.com \
--to=fuga@studiofuga.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