From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Johannes Berg <johannes@sipsolutions.net>
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 22:04:46 +1000 [thread overview]
Message-ID: <1147349086.20614.30.camel@localhost.localdomain> (raw)
In-Reply-To: <1147348702.9630.7.camel@johannes>
On Thu, 2006-05-11 at 13:58 +0200, Johannes Berg wrote:
> 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.
kmix looks approx. ok
> Anyone up to inventing a new mixer API that uses sysfs? ;)
>
> johannes
prev parent reply other threads:[~2006-05-11 12:04 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
2006-05-11 12:04 ` Benjamin Herrenschmidt [this message]
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=1147349086.20614.30.camel@localhost.localdomain \
--to=benh@kernel.crashing.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).