From: Saul Wold <sgw@linux.intel.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] alsa-state: Provide an empty asound.conf by default
Date: Tue, 09 Jul 2013 16:32:23 -0700 [thread overview]
Message-ID: <51DC9D87.1000604@linux.intel.com> (raw)
In-Reply-To: <1373410775.3429.19.camel@envy.home>
On 07/09/2013 03:59 PM, Darren Hart wrote:
> On Tue, 2013-07-09 at 15:43 -0700, Saul Wold wrote:
>> On 07/09/2013 03:15 PM, Darren Hart wrote:
>>> An empty asound.conf should work for most cases. The existing asound.conf
>>> uses plug dmix which causes arecord to fail without a special -D device
>>> specification on the command line (as no capture device is defined).
>>>
>>> Clear asound.conf for the default case. Any needed changes should be
>>> made in the BSP layers.
>>>
>> Does there need to be any corresponding change for the meta-yocto-bsps?
>
> I don't believe so, but I have not built and tested every one. The old
> one setup an alias "mixer0" to hardware card 0, which isn't necessary
> for alsamixer to work and should be the default anyway.
>
> I don't know what the motivation was to use dmix for the default pcm.
> This was pulled in from open-embedded, which has a minimal commit
> message:
>
> commit bbc2776c0d955da7ec774ae934c541f33133f876
> Author: Michael Lauer <mickey@vanille-media.de>
> Date: Thu Sep 13 01:10:23 2007 +0000
>
Given it's 5 years old, it might be that alsa now "does the right thing"
and your change is valid.
Thanks
Sau!
> alsa-state: ship standard asoundrc (simple dmix configuration)
> that should be a reasonable default for most devices
>
> According to the alsa wiki, the asound.conf should not be required for
> basic functionality:
>
> http://www.alsa-project.org/main/index.php/Asoundrc
>
> --
> Darren
>
>>
>>
>> Sau!
>>
>>
>>> Signed-off-by: Darren Hart <dvhart@linux.intel.com>
>>> Cc: Koen Kooi <koen@dominion.thruhere.net>
>>> ---
>>> meta/recipes-bsp/alsa-state/alsa-state/asound.conf | 13 +------------
>>> 1 file changed, 1 insertion(+), 12 deletions(-)
>>>
>>> diff --git a/meta/recipes-bsp/alsa-state/alsa-state/asound.conf b/meta/recipes-bsp/alsa-state/alsa-state/asound.conf
>>> index 6be0242..03653cf 100644
>>> --- a/meta/recipes-bsp/alsa-state/alsa-state/asound.conf
>>> +++ b/meta/recipes-bsp/alsa-state/alsa-state/asound.conf
>>> @@ -1,12 +1 @@
>>> -# default dmix configuration
>>> -
>>> -pcm.!default {
>>> - type plug
>>> - slave.pcm "dmix"
>>> -}
>>> -
>>> -ctl.mixer0 {
>>> - type hw
>>> - card 0
>>> -}
>>> -
>>> +# Global alsa-lib configuration
>>>
>
next prev parent reply other threads:[~2013-07-09 23:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 22:15 [PATCH] alsa-state: Provide an empty asound.conf by default Darren Hart
2013-07-09 22:43 ` Saul Wold
2013-07-09 22:59 ` Darren Hart
2013-07-09 23:32 ` Saul Wold [this message]
2013-07-10 16:52 ` Darren Hart
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=51DC9D87.1000604@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=dvhart@linux.intel.com \
--cc=koen@dominion.thruhere.net \
--cc=openembedded-core@lists.openembedded.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