All of lore.kernel.org
 help / color / mirror / Atom feed
From: pl bossart <bossart.nospam@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, lrg@slimlogic.co.uk
Subject: Re: UCM questions
Date: Fri, 21 Jan 2011 14:53:30 -0600	[thread overview]
Message-ID: <AANLkTim_Q=oTfHS33R2hf6B3gC1Dj2fpiCAjfa7kJFw7@mail.gmail.com> (raw)
In-Reply-To: <20110121164329.GB6200@opensource.wolfsonmicro.com>

>> I am fine with a system-specific configuration file for each use case,
>> but if I have to change the defines in alsa-lib it's a bit of a pain.
>> It'll imply branches and specific packages just for a stupid include
>> file.
>
> If the define isn't there you should just be able to use a string - no
> need to update the header file unless the thing being added is
> sufficiently general that it seems like a good idea.

I think I am missing something here.
First I believe there's only one application (PulseAudio or resource
management of some sort) that will talk to UCM. Player applications
shouldn't know anything about UCM, right? You would end-up making
conflicting decisions.
Next, if everyone can add #defines and craft new strings to represent
verbs, this central application/module will either ask for use cases
that are not supported everywhere, or limit itself to 'common' use
cases. Or do we expect to rewrite this on each and every platform?
Wouldn't it make sense to avoid branches and proliferation by limiting
the definition of use cases and instead only allow for changes in
configuration files?

  reply	other threads:[~2011-01-21 20:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 22:06 UCM questions pl bossart
2011-01-21 11:37 ` Mark Brown
2011-01-21 15:12   ` pl bossart
2011-01-21 16:43     ` Mark Brown
2011-01-21 20:53       ` pl bossart [this message]
2011-01-21 23:37         ` Liam Girdwood
2011-01-22  5:22           ` Raymond Yau
2011-01-23  0:41         ` Mark Brown
2011-01-23 13:49         ` Jaroslav Kysela
2011-01-21 15:24   ` Liam Girdwood
2011-01-21 21:03     ` pl bossart
2011-01-21 23:37       ` Liam Girdwood
2011-01-23 13:39       ` Jaroslav Kysela
2011-01-24 22:31         ` pl bossart
2011-01-25 12:13           ` Liam Girdwood
2011-01-25 21:58             ` pl bossart

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='AANLkTim_Q=oTfHS33R2hf6B3gC1Dj2fpiCAjfa7kJFw7@mail.gmail.com' \
    --to=bossart.nospam@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@slimlogic.co.uk \
    /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.