Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] task-base: add alsa-state to task-base-alsa
Date: Thu, 12 Jan 2012 17:31:28 +0100	[thread overview]
Message-ID: <20120112163127.GG3452@jama.jama.net> (raw)
In-Reply-To: <4F0F08F4.4010505@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 1854 bytes --]

On Thu, Jan 12, 2012 at 08:23:16AM -0800, Darren Hart wrote:
> 
> 
> On 01/10/2012 09:39 AM, Joshua Lock wrote:
> > This enables automatic configuration setting and restoration on systems
> > with alsa.
> > 
> > Signed-off-by: Joshua Lock <josh@linux.intel.com>
> 
> Acked-by: Darren Hart <dvhart@linux.intel.com>

can we use VIRTUAL_RUNTIME for this, please?

for example in SHR we have alsa-state provided by fsoaudiod

Cheers,

> 
> > ---
> >  meta/recipes-core/tasks/task-base.bb |    5 +++--
> >  1 files changed, 3 insertions(+), 2 deletions(-)
> > 
> > diff --git a/meta/recipes-core/tasks/task-base.bb b/meta/recipes-core/tasks/task-base.bb
> > index e0960b5..7460be4 100644
> > --- a/meta/recipes-core/tasks/task-base.bb
> > +++ b/meta/recipes-core/tasks/task-base.bb
> > @@ -2,7 +2,7 @@ DESCRIPTION = "Merge machine and distro options to create a basic machine task/p
> >  LICENSE = "MIT"
> >  LIC_FILES_CHKSUM = "file://${COREBASE}/LICENSE;md5=3f40d7994397109285ec7b81fdeb3b58 \
> >                      file://${COREBASE}/meta/COPYING.MIT;md5=3da9cfbcb788c80a0384361b4de20420"
> > -PR = "r72"
> > +PR = "r73"
> >  
> >  inherit task
> >  
> > @@ -183,7 +183,8 @@ RRECOMMENDS_task-base-vfat = "\
> >  
> >  RDEPENDS_task-base-alsa = "\
> >      alsa-utils-alsactl \
> > -    alsa-utils-alsamixer"
> > +    alsa-utils-alsamixer \
> > +    alsa-state"
> >  
> >  RRECOMMENDS_task-base-alsa = "\
> >      kernel-module-snd-mixer-oss \
> 
> -- 
> Darren Hart
> Intel Open Source Technology Center
> Yocto Project - Linux Kernel
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2012-01-12 16:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-10 17:39 [PATCH 0/3] Add alsa-state from OE Classic v2 Joshua Lock
2012-01-10 17:39 ` [PATCH 1/3] alsa-state: add alsa-state from oe classic Joshua Lock
2012-01-10 19:30   ` Otavio Salvador
2012-01-10 19:44     ` Joshua Lock
2012-01-12 16:22   ` Darren Hart
2012-01-10 17:39 ` [PATCH 2/3] alsa-state: move state files to localstatedir Joshua Lock
2012-01-12 16:23   ` Darren Hart
2012-01-10 17:39 ` [PATCH 3/3] task-base: add alsa-state to task-base-alsa Joshua Lock
2012-01-12 16:23   ` Darren Hart
2012-01-12 16:31     ` Martin Jansa [this message]
2012-01-13 18:54       ` Joshua Lock
2012-01-13 18:58         ` Martin Jansa
2012-01-10 19:34 ` [PATCH 0/3] Add alsa-state from OE Classic v2 Otavio Salvador
2012-01-10 19:45   ` Joshua Lock
2012-01-10 19:48     ` Otavio Salvador
2012-01-24 23:37   ` Joshua Lock

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=20120112163127.GG3452@jama.jama.net \
    --to=martin.jansa@gmail.com \
    --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