Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] AT91SAM9G20-EK and aplay
Date: Tue, 28 May 2013 19:02:20 +0200	[thread overview]
Message-ID: <51A4E31C.7060707@mind.be> (raw)
In-Reply-To: <51A3355D.3070209@scen.it>

On 27/05/13 12:28, Carlo Rajko wrote:
> Il 27/05/2013 11:16, Thomas Petazzoni ha scritto:
>> Dear Carlo Rajko,
>>
>> On Mon, 27 May 2013 10:03:50 +0200, Carlo Rajko wrote:
>>
>>>> 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.
>>>
>>> I switch to CS 2011.09 and now is ok, thanks.
>>
>> It's a problem worth reporting to Mentor Graphics, IMO.
>>
>> Even though I doubt anything will happen, last time I reported a bug,
>> nothing really happened, unfortunately.
>
> I'll try with the new version 2013.05, just available in the package
> buildroot, maybe the problem is already solved.

  We should probably blacklist the failing CS toolchains for the 
arm926ej-s, then.

  Regards,
  Arnout


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2013-05-28 17:02 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
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 [this message]
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=51A4E31C.7060707@mind.be \
    --to=arnout@mind.be \
    --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