From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH 0/2] Add alsa-state from OE Classic
Date: Tue, 03 Jan 2012 16:43:00 -0800 [thread overview]
Message-ID: <4F03A094.3050803@linux.intel.com> (raw)
In-Reply-To: <cover.1325557342.git.josh@linux.intel.com>
On 01/02/2012 06:26 PM, Joshua Lock wrote:
> Please review the following changes for suitability for inclusion. If you have
> any objections or suggestions for improvement, please respond to the patches. If
> you agree with the changes, please provide your Acked-by.
>
> The small series following introduces the alsa-state recipe from oe-classic.
> The reason for doing so is to remove the requirement for recipes like the
> beagleboard-audio recipe in meta-yocto, which ensures the beagleboards sound
> device has the volume turned up.
>
> Long term I'd like to implement something more generic for handling device quirks,
> but alsa-state is a simple fix for an immediate need that should standardise how
> alsa configuration is handled in layers.
>
Will this address the similar issue that the n450-audio recipe does in
the meta-intel layer? The n450 seems to use amixer and not alsactl.
And if so, can you provide a patch for meta-intel?
Sau!
> Cheers.
> Joshua
>
> The following changes since commit 8f348ccad083d6c02c200652ff6295e701e88f0d:
>
> coreutils: ensure --color works so DEPEND on libcap (2011-12-24 10:05:35 +0000)
>
> are available in the git repository at:
> git://git.openembedded.org/openembedded-core-contrib josh/devices
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=josh/devices
>
> Joshua Lock (2):
> alsa-state: add alsa-state from oe classic
> task-base: add alsa-state to task-base-alsa
>
> meta/recipes-bsp/alsa-state/alsa-state.bb | 57 ++++++++++++++++++++
> meta/recipes-bsp/alsa-state/alsa-state/alsa-state | 29 ++++++++++
> meta/recipes-bsp/alsa-state/alsa-state/asound.conf | 12 ++++
> .../recipes-bsp/alsa-state/alsa-state/asound.state | 1 +
> meta/recipes-core/tasks/task-base.bb | 5 +-
> 5 files changed, 102 insertions(+), 2 deletions(-)
> create mode 100644 meta/recipes-bsp/alsa-state/alsa-state.bb
> create mode 100755 meta/recipes-bsp/alsa-state/alsa-state/alsa-state
> create mode 100644 meta/recipes-bsp/alsa-state/alsa-state/asound.conf
> create mode 100644 meta/recipes-bsp/alsa-state/alsa-state/asound.state
>
next prev parent reply other threads:[~2012-01-04 0:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 2:26 [RFC PATCH 0/2] Add alsa-state from OE Classic Joshua Lock
2012-01-03 2:26 ` [RFC PATCH 1/2] alsa-state: add alsa-state from oe classic Joshua Lock
2012-01-03 2:26 ` [RFC PATCH 2/2] task-base: add alsa-state to task-base-alsa Joshua Lock
2012-01-04 0:43 ` Saul Wold [this message]
2012-01-04 0:53 ` [RFC PATCH 0/2] Add alsa-state from OE Classic 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=4F03A094.3050803@linux.intel.com \
--to=sgw@linux.intel.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