All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@suse.cz>
Cc: alsa-devel <alsa-devel@lists.sourceforge.net>,
	James Courtier-Dutton <James@superbug.co.uk>
Subject: Re: [RFC] Extra info via the TLV interface
Date: Tue, 05 Sep 2006 12:44:50 +0200	[thread overview]
Message-ID: <s5h3bb6k2xp.wl%tiwai@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0609050818500.9338@tm8103.perex-int.cz>

At Tue, 5 Sep 2006 08:30:42 +0200 (CEST),
Jaroslav Kysela wrote:
> 
> On Mon, 4 Sep 2006, Takashi Iwai wrote:
> 
> > Sorry, I meant to re-define every control "name" that is not
> > conforming in the above.  Renaming a mixer element _always_ results in
> > a name mismatch _error_ in alsactl.  It's handled as an error, not a
> > warning.
> 
> Note that alsactl or probably alsa-lib should be improved. We cannot 
> expect that names won't change and name cleanups are preferred. I would 
> propose to create a database with name change description to prevent these 
> errors and allow users switching between two ALSA driver versions more 
> nicely.
> 
> The question is, if applications use these names to do something special
> (if they compares them with own strings). Of course, we will break the 
> compatibility in this case. I would like to discuss, if adding a function
> like
> 
> int snd_mixer_compat_control_name(const char *name,
> 				  const char *alsa_version,
> 			          char *new_name, int new_name_size)
> 
> would be sufficient to ALSA API.

Hmm...  How would this function be used?
I still don't get it.  Is it a function to be called by apps, or a
function used in alsa-lib internaly?


Takashi

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

  reply	other threads:[~2006-09-05 10:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-04 12:48 [RFC] Extra info via the TLV interface James Courtier-Dutton
2006-09-04 13:04 ` Jaroslav Kysela
2006-09-04 13:30   ` Liam Girdwood
2006-09-04 13:14 ` Liam Girdwood
2006-09-04 14:13 ` Takashi Iwai
2006-09-04 15:31   ` James Courtier-Dutton
2006-09-04 15:42     ` Takashi Iwai
2006-09-05  6:30       ` Jaroslav Kysela
2006-09-05 10:44         ` Takashi Iwai [this message]
2006-09-05 15:32           ` Jaroslav Kysela
2006-09-05 15:37             ` Takashi Iwai

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=s5h3bb6k2xp.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=James@superbug.co.uk \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=perex@suse.cz \
    /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.