All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/4] Add alsa-state from OE Classic v3
Date: Tue, 24 Jan 2012 15:15:33 -0800	[thread overview]
Message-ID: <4F1F3B95.4070105@linux.intel.com> (raw)
In-Reply-To: <09C174D7-2741-4099-BBA1-861E3608EB98@dominion.thruhere.net>

On 24/01/12 07:02, Koen Kooi wrote:
>
> Op 13 jan. 2012, om 20:10 heeft Joshua Lock het volgende geschreven:
>
>> The small series which follows 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.
>
> FWIW, alsa-lib itself includes initscripts to do this. I dropped asound.state in /var/lib/alsa and it just worked since alsactl also installs systemd units to handle this. So alsa-state can just hold the config files and drop the initscripts by the looks of it.

Thanks for raising this, I hadn't seen that alsa-utils provides some 
extras with alsactl.

Taking a quick look I see that they ship systemd units for state save 
and restore and a udev rule for restoring the state.

I can't see any initscript, so I think switching to what's provided by 
alsa-utils would mean losing state saving for non-systemd folk but 
systemd users can probably just set VIRTUAL-RUNTIME_alsa-state = 
"alsa-utils-alsactl".

I am an alsa newb so if I'm missing something please point me at it.

Cheers,
Joshua
-- 
Joshua Lock
         Yocto Project "Johannes factotum"
         Intel Open Source Technology Centre



  reply	other threads:[~2012-01-24 23:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-13 19:10 [PATCH 0/4] Add alsa-state from OE Classic v3 Joshua Lock
2012-01-13 19:10 ` [PATCH 1/4] task-base: move default definition of VIRTUAL-RUNTIME_apm Joshua Lock
2012-01-13 19:10 ` [PATCH 2/4] alsa-state: add alsa-state from oe classic Joshua Lock
2012-01-13 19:10 ` [PATCH 3/4] alsa-state: move state files to localstatedir Joshua Lock
2012-01-13 19:10 ` [PATCH 4/4] task-base: add VIRTUAL-RUNTIME_alsa-state to task-base-alsa Joshua Lock
2012-01-17 19:40 ` [PATCH 0/4] Add alsa-state from OE Classic v3 Saul Wold
2012-01-24 15:02 ` Koen Kooi
2012-01-24 23:15   ` Joshua Lock [this message]
2012-01-26 23:09     ` Otavio Salvador
2012-01-27  8:00       ` Koen Kooi
2012-01-27 18:49         ` 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=4F1F3B95.4070105@linux.intel.com \
    --to=josh@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 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.