linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	ALSA development <alsa-devel@alsa-project.org>
Subject: Re: [Alsa-devel] [RFC] alsa integer control ranges
Date: Tue, 16 May 2006 14:27:12 +0200	[thread overview]
Message-ID: <s5h7j4m40kf.wl%tiwai@suse.de> (raw)
In-Reply-To: <1147780945.29795.110.camel@johannes>

At Tue, 16 May 2006 14:02:20 +0200,
Johannes Berg wrote:
> 
> Apparently all alsa userspace programs including alsamixer suck. Hence,
> this patch is required to make them work properly. Why is it so hard to
> do these additions/subtractions in the program or maybe even in the alsa
> library? The alsa libraries already think they know better and mess up
> all kinds of things.

It's a pretty stupid question to ask why you are stupid :)

I don't think it's alsa-lib that prevents the negative or non-zero
integer range.  The fact amixer works implies that it's an
app-specific bug.  But I'm not 100% sure and need more
inside-looking.

> What are your opinions on this? Should this be required? And if so, why
> do we even have the value.integer.min when we can't use it anyway? 

Right now, the range 0-max would make your life easier, I guess.

The min value is an API definition, and implemented and worked once.
But no drivers used yet.  So, there might be a breakage.  It's of
course to be fixed.


Takashi

  reply	other threads:[~2006-05-16 12:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16 12:02 [RFC] alsa integer control ranges Johannes Berg
2006-05-16 12:27 ` Takashi Iwai [this message]
2006-05-16 22:03   ` [Alsa-devel] " Benjamin Herrenschmidt
2006-05-17  9:59     ` Takashi Iwai
2006-05-17 12:16       ` Johannes Berg
2006-05-17 12:35         ` Takashi Iwai
2006-05-17 12:39           ` Johannes Berg
2006-05-17 21:41           ` Benjamin Herrenschmidt
2006-05-17 12:17   ` Johannes Berg
2006-05-17 12:37     ` Takashi Iwai
2006-05-16 12:31 ` Jaroslav Kysela
2006-05-16 22:04   ` Benjamin Herrenschmidt
2006-05-17  6:41     ` Jaroslav Kysela
2006-05-17 12:21       ` Johannes Berg
2006-05-17  9:47     ` Takashi Iwai
2006-05-17 12:24       ` Johannes Berg
2006-05-16 14:53 ` Lee Revell
2006-05-16 14:55   ` Johannes Berg
2006-05-17 15:38     ` Wolfgang Pfeiffer
2006-05-16 22:00 ` Benjamin Herrenschmidt
2006-05-16 22:04   ` [Alsa-devel] " Lee Revell

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=s5h7j4m40kf.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=johannes@sipsolutions.net \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).