[Alsa-devel] [RFC] alsa integer control ranges

Johannes Berg johannes at sipsolutions.net
Wed May 17 22:21:10 EST 2006


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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 793 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ozlabs.org/pipermail/linuxppc-dev/attachments/20060517/279c4481/attachment.pgp>


More information about the Linuxppc-dev mailing list