From: yegor_sub1@visionsystems.de (Yegor Yefremov)
To: linux-arm-kernel@lists.infradead.org
Subject: AC97 audio broken on SAM9263EK?
Date: Wed, 10 Mar 2010 16:41:00 +0100 [thread overview]
Message-ID: <4B97BD8C.3030502@visionsystems.de> (raw)
In-Reply-To: <4B97602C.6070608@atmel.com>
>> I tried both files and the one really working is ac97c_alsa.c. As far
>> as I understand it is combination of both patches for at91 support and
>> full duplex?
>>
>> I've tried the following applications under Debian 5.0:
>>
>> mpg123
>> vlc
>> mplayer
>> amarok
>>
>> Regards,
>> Yegor
>>
>
> ac97c_alsa.c is the result of the 2 patches I have send to the alsa
> mailing list
> (http://mailman.alsa-project.org/pipermail/alsa-devel/2010-March/025709.html
> and
> http://mailman.alsa-project.org/pipermail/alsa-devel/2010-February/025628.html).
> It indeed adds support for AT91(1/2) and full duplex(2/2).But is is
> strange that if you only apply only the first patch you encounter errors...
>
> On my side I have only tested these patches with mplayer and aplay.
> Plus to test the full duplex I have done like this:
> "arecord -d 10 -f cd -t wav test.wav & mplayer my_file.mp3"
When do you think the driver could hit the mainline kernel? Till 2.6.35 open window?
Best regards,
Yegor
next prev parent reply other threads:[~2010-03-10 15:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 19:06 AC97 audio broken on SAM9263EK? Bill Gatliff
2010-02-25 10:09 ` Sedji Gaouaou
2010-02-25 12:46 ` Bill Gatliff
2010-02-25 16:49 ` Sedji Gaouaou
2010-02-28 3:23 ` Bill Gatliff
2010-03-01 10:34 ` Sedji Gaouaou
2010-03-09 14:11 ` Yegor Yefremov
2010-03-09 15:17 ` Sedji Gaouaou
2010-03-10 8:47 ` Yegor Yefremov
2010-03-10 9:02 ` Sedji Gaouaou
2010-03-10 15:41 ` Yegor Yefremov [this message]
2010-03-10 15:53 ` Sedji Gaouaou
2010-06-01 13:39 ` Yegor Yefremov
2010-06-03 12:46 ` Sedji Gaouaou
2010-06-03 14:02 ` Yegor Yefremov
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=4B97BD8C.3030502@visionsystems.de \
--to=yegor_sub1@visionsystems.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.