From: Michael Trimarchi <trimarchimichael@yahoo.it>
To: buildroot@busybox.net
Subject: [Buildroot] at91sam9260 alsa problem
Date: Mon, 1 Nov 2010 10:55:29 +0000 (GMT) [thread overview]
Message-ID: <811511.24510.qm@web29618.mail.ird.yahoo.com> (raw)
In-Reply-To: <262336.75716.qm@web29607.mail.ird.yahoo.com>
Hi
----- Messaggio originale -----
> Da: Michael Trimarchi <trimarchimichael@yahoo.it>
> A: Michael Trimarchi <trimarchimichael@yahoo.it>; buildroot at busybox.net
> Inviato: Lun 1 novembre 2010, 11:43:13
> Oggetto: Re: [Buildroot] at91sam9260 alsa problem
>
>
>
> Hi all
>
> maybe this one is the right configuration of the machine in buildroot
>
> BR2_ARM_OABI=y
> BR2_ARCH="arm"
> BR2_ENDIAN="LITTLE"
> BR2_GCC_TARGET_TUNE="arm9tdmi"
> BR2_GCC_TARGET_ARCH="armv4t"
sorry this is the arm5te
Michael
> BR2_GCC_TARGET_ABI="apcs-gnu"
>
> I have seen a lot of mailing list and different people report some strange
> problem with alsa. I'm using
> a 2.6.29.3 kernel revision
>
> Michael
>
>
> ----- Messaggio originale -----
> > Da: Michael Trimarchi <trimarchimichael@yahoo.it>
> > A: buildroot at busybox.net
> > Inviato: Lun 1 novembre 2010, 10:40:30
> > Oggetto: [Buildroot] at91sam9260 alsa problem
> >
> > Hi all
> >
> > I have compiled the linux kernel (2.6.29) with EABI option disable so the
> > expected compiled option is:
> >
> > -mpcu=apcs-gnu
> >
> > I have the same compiled option in buildroot and now the amixer and
>alsamixer
>
>
> > works but aplay and arecord
> >
> > report this error:
> >
> > set_params: Channels count non available
> >
> > Compile the kernel using eabi and oabi compatible give different error.
> >
> > This is the relevant part of buildroot config
> >
> > BR2_ARM_TYPE="GENERIC_ARM"
> > # BR2_ARM_EABI is not set
> > BR2_ARM_OABI=y
> > BR2_ARCH="arm"
> > BR2_ENDIAN="LITTLE"
> > BR2_GCC_TARGET_ABI="apcs-gnu"
> >
> > #
> > # Target options
> > #
> >
> > #
> > # Preset Devices
> > #
> > # BR2_TARGET_ARMLTD is not set
> > BR2_BOARD_NAME="at91sam9260dfc"
> > BR2_BOARD_PATH="target/device/Atmel/$(BR2_BOARD_NAME)"
> >
> > and this is the relevant part of the kernel
> >
> > # CONFIG_AEABI is not set
> >
> > With other combination I can use playback and record facilites but the
>mixer
>
> > doesn't
> > work for the size of the parameteres during kernel syscall
> >
> > Best regards
> > Michael Trimarchi
> >
> >
> >
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot
> >
>
>
>
>
next prev parent reply other threads:[~2010-11-01 10:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-01 9:40 [Buildroot] at91sam9260 alsa problem Michael Trimarchi
2010-11-01 10:43 ` Michael Trimarchi
2010-11-01 10:55 ` Michael Trimarchi [this message]
2010-11-01 19:43 ` Michael Trimarchi
2010-11-02 14:23 ` Peter Korsgaard
2010-11-02 14:43 ` Michael Trimarchi
2010-11-02 16:34 ` Michael Trimarchi
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=811511.24510.qm@web29618.mail.ird.yahoo.com \
--to=trimarchimichael@yahoo.it \
--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