From: Johannes Berg <johannes@sipsolutions•net>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs•org>
Subject: Re: Alubook 5,8: No sound with 2.6.17-rc3-g5528e568-dirty
Date: Thu, 11 May 2006 13:58:22 +0200 [thread overview]
Message-ID: <1147348702.9630.7.camel@johannes> (raw)
In-Reply-To: <1147304824.32448.82.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 633 bytes --]
On Thu, 2006-05-11 at 09:47 +1000, Benjamin Herrenschmidt wrote:
> Same as mine, it works fine with snd-aoa
I should build a database with a machine string -> user* mapping... This
means that even my brother has this one and it works great with snd-aoa
as far as I know :)
Though, since the alsa userspace libs absolutely *SUCK* no program I
know of can properly represent the mixer controls except maybe amixer...
I'd hate to work around this in the kernel, but the alsa libs are such
complex beasts that I have a feeling they won't be fixed.
Anyone up to inventing a new mixer API that uses sysfs? ;)
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-11 11:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 15:49 Alubook 5,8: No sound with 2.6.17-rc3-g5528e568-dirty Wolfgang Pfeiffer
2006-05-10 16:04 ` Johannes Berg
2006-05-10 17:24 ` Wolfgang Pfeiffer
2006-05-10 20:54 ` Christoph Cebulla
2006-05-10 23:48 ` Benjamin Herrenschmidt
2006-05-10 21:30 ` Wolfgang Pfeiffer
2006-05-10 23:08 ` Wolfgang Pfeiffer
2006-05-10 23:49 ` Benjamin Herrenschmidt
2006-05-12 14:19 ` Wolfgang Pfeiffer
2006-05-12 14:27 ` Johannes Berg
2006-05-10 23:47 ` Benjamin Herrenschmidt
2006-05-11 11:58 ` Johannes Berg [this message]
2006-05-11 12:04 ` Benjamin Herrenschmidt
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=1147348702.9630.7.camel@johannes \
--to=johannes@sipsolutions$(echo .)net \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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