From: Johannes Berg <johannes@sipsolutions.net>
To: Jaroslav Kysela <perex@suse.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Benjamin Berg <benjamin@sipsolutions.net>,
linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [Alsa-devel] [RFC] alsa integer control ranges
Date: Wed, 17 May 2006 14:21:10 +0200 [thread overview]
Message-ID: <1147868470.15507.9.camel@johannes> (raw)
In-Reply-To: <Pine.LNX.4.61.0605170836470.10248@tm8103.perex-int.cz>
[-- Attachment #1: Type: text/plain, Size: 827 bytes --]
On Wed, 2006-05-17 at 08:41 +0200, Jaroslav Kysela wrote:
> It's better to have problematic values by default and define a module
> (driver) option to enable the "compatible" behaviour.
I just committed the patch to be always compatible. I'm not going to
clutter the code even more.
> Otherwise the apps
> will be never fixed.
True.
> Also, ideally, you can fix apps and send patches to
> authors and/or create problematic controls in the dummy driver
> (drivers/dummy.c) and send a notice to app developers that they have
> broken apps and ask to fix them refering to the dummy driver test case.
The dummy driver isn't a bad idea, all the rest is. There are *dozens*
of broken apps, and most of their code is horrid. I couldn't even fix
alsamixer for the 3..28 range brokenness.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]
next prev parent reply other threads:[~2006-05-17 12:21 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 ` [Alsa-devel] " Takashi Iwai
2006-05-16 22:03 ` 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 [this message]
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=1147868470.15507.9.camel@johannes \
--to=johannes@sipsolutions.net \
--cc=alsa-devel@alsa-project.org \
--cc=benjamin@sipsolutions.net \
--cc=linuxppc-dev@ozlabs.org \
--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 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).