Hi there!

FWIW, I haven't had the time to look deep into this issues.

On Tue, 30 Sep 2008 12:24:21 +0200, Timo Juhani Lindfors wrote:
> Joachim Breitner <[EMAIL PROTECTED]> writes:
>> I’m not sure how well that would work with the revamped sound handling
>> in the next release of the framework, maybe Guillaume or whoever works
>
> There is now a 'scenario_dir' option in frameworkd.conf which defaults
> to /etc/alsa/scenario

These scenarios doesn't belong to ALSA and, even "worse", are not
directly managed by any upstream ALSA utils.  Instead, they're specific
to frameworkd: why not default to /etc/freesmartphone/scenarios?

This is how I see it, from an outside POV, but still according to the
FHS [1]:

- /usr/share/freesmartphone/scenarios
  default scenarios, not to be modified by the end-users since they are
  in a read-only "position" [2]

- /etc/freesmarphone/scenarios
  modified scnearios, since they are configuration files [3]

When frameworkd needs a scenario it looks for it in /e/f/s/ and if it
doesn't find it it loads the default one, i.e. the one from /u/s/f/s/.

I can see only one problem with /u/s/f/s/: usually, there's not one
general scenario, but each one is specific to the sound chip.  In this
case, the solution would be something like

  /etc/frameworkd.conf:
    [odeviced.audio]
    # this is for unmodified scenarios, please don't change it
    default_scenarios_dir = /usr/share/openmoko/scenarios/
    # this is for customized scenarios
    scenarios_dir = /etc/freesmarphone/scenarios

This will also help each distribution (like Debian) to untight scenarios
file from frameworkd: e.g., Debian could ship frameworkd "binaries" in
fso-frameworkd and scenarios in openmoko-scenarios [4].

On Debian, one thing that you should consider about mixer levels is that
as soon as you install alsa-utils, by default mixer levels are stored
and restored on shutdown and bootup, respectively.

> how about migrating the debian package to use that?

This is clearly an upstream problem, which means that I'd prefer to wait
for upstream to solve it :-D

Thx, bye,
Gismo / Luca

Footnotes: 
[1] http://www.pathname.com/fhs/
[2] http://www.pathname.com/fhs/pub/fhs-2.3.html#PURPOSE18
[3] http://www.pathname.com/fhs/pub/fhs-2.3.html#PURPOSE6
[4] this package name is just an *example*

Attachment: pgpVSbu9flBGU.pgp
Description: PGP signature

Reply via email to