Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] AT91SAM9G20-EK and aplay
Date: Fri, 24 May 2013 09:50:46 -0300	[thread overview]
Message-ID: <519F6226.4060002@zacarias.com.ar> (raw)
In-Reply-To: <519F452D.4070505@scen.it>

On 05/24/2013 07:47 AM, Carlo Rajko wrote:
>>> I think the problem is not in aply because I have the same problem with
>>> mpg123.
>>> Could be the library alsa?
>>
>> It could. But at least gdb will tell us if it's an undefined
>> instruction, an invalid memory access, an unaligned access, or
>> something else.

Actually it's the toolchain, seems CS 2012.03 isn't emitting proper
arm926ej-s code.
I've managed to reproduce it with the qemu_arm_versatile sample
configuration and adding a bunch of packages (mpg123, vorbis-tools, ...)
It did strike me as odd that i've got the same failures as yours (aplay,
mpg123) but ogg123 worked fine with alsa output.
So switching to an internal toolchain or CS 2011.09 magically fixed the
issues.
Regards.

  reply	other threads:[~2013-05-24 12:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24  7:36 [Buildroot] AT91SAM9G20-EK and aplay Carlo Rajko
2013-05-24  8:05 ` Thomas Petazzoni
2013-05-24  9:03   ` Carlo Rajko
2013-05-24  9:23     ` Thomas Petazzoni
2013-05-24 10:47       ` Carlo Rajko
2013-05-24 12:50         ` Gustavo Zacarias [this message]
2013-05-27  8:03           ` Carlo Rajko
2013-05-27  9:16             ` Thomas Petazzoni
2013-05-27 10:28               ` Carlo Rajko
2013-05-28 17:02                 ` Arnout Vandecappelle
2013-05-29 15:15                   ` Carlo Rajko
2013-07-04  9:02           ` Aleksandar Zivkovic

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=519F6226.4060002@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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