All of lore.kernel.org
 help / color / mirror / Atom feed
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 15:43:26 -0700	[thread overview]
Message-ID: <51DC920E.1040305@linux.intel.com> (raw)
In-Reply-To: <e01e4656b562f087f270dc1134e7501c8f6b169b.1373408128.git.dvhart@linux.intel.com>

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?


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
>


  reply	other threads:[~2013-07-09 22:43 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 [this message]
2013-07-09 22:59   ` Darren Hart
2013-07-09 23:32     ` Saul Wold
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=51DC920E.1040305@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 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.