From: "Gaëtan Carlier" <gcembed@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: alsa-devel@alsa-project.org,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: mx27_3ds : Sound doesn't work anymore on linux-next
Date: Fri, 17 Aug 2012 17:28:41 +0200 [thread overview]
Message-ID: <502E6329.60308@gmail.com> (raw)
In-Reply-To: <502E6033.4010805@gmail.com>
Just some more informations, process enter in D+ state and this is so
impossible to kill them.
On 08/17/2012 05:16 PM, Gaëtan Carlier wrote:
> Hi,
> It is several days that I tried to make sound work on mx27_3ds platform
> from linux-next (daily cloned/pulled) but each time I try start start
> aplay or alsamixer, the process freeze and CTRL+C has not effect. I can
> open another SSH session and execute other commands but alsa commands
> always freeze.
> The sound card is correctly installer at boot :
>
> imx_mc13783 imx_mc13783.0: mc13783-hifi <-> imx-ssi.0 mapping ok
> ALSA device list:
> #0: imx_mc13783
>
> I only apply the patch "[PATCH 1/2] ARM: mx27pdk: Add audio support". I
> attach my config file.
>
> I try to apply patch on a previous commit when I told that this patch
> was working but it didn't succeed the is still freezing.
> I try to make it working on another mx27-based platform but same
> problem. I try to update Alsa from version 1.0.23 to 1.0.25 but same
> behaviour.
> What is wrong ?
>
> Regards,
> Gaëtan Carlier.
Regards,
Gaëtan.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2012-08-17 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 15:16 mx27_3ds : Sound doesn't work anymore on linux-next Gaëtan Carlier
2012-08-17 15:28 ` Gaëtan Carlier [this message]
2012-08-21 15:14 ` Gaëtan Carlier
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=502E6329.60308@gmail.com \
--to=gcembed@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=festevam@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).