linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollis@penguinppc.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
	debian-powerpc <debian-powerpc@lists.debian.org>
Subject: Re: snd-aoa status update / automatic driver loading
Date: Mon, 22 May 2006 22:11:38 -0500	[thread overview]
Message-ID: <20060522221138.683790c2@diesel> (raw)
In-Reply-To: <1147860564.14395.6.camel@johannes>

On Wed, 17 May 2006 12:09:24 +0200
Johannes Berg <johannes@sipsolutions.net> wrote:
> 
> Currently snd-aoa is known to work on the following machines:
> * PowerBook5,8
> * PowerBook5,7
> * PowerMac8,1
> * PowerMac8,2
> * 17" October 2005 PowerBook (don't know the number)
> * PowerMac11,2
> * PowerBook6,8
> and my
> * PowerBook5,6
> 
> People with those machines are encouraged to use and stress-test it,
> it also provides much better hardware support than snd-powermac, for
> example it can actually reprogram the hardware if you have a 48KHz
> file instead of having to digitally downsample it to 44.1KHz like
> required with snd-powermac in most cases.

The "auto-loading" stuff doesn't seem to be working for me on my
PowerMac11,2, with a fresh git clone as of right now. What is the base
module that should load all the others? After a "make install", I still
had to modprobe almost everything by hand (`find ./snd-aoa -name \*.ko`
in the source directory to get a list).

When the driver finally did completely load, I saw this in dmesg:
snd-aoa-codec-tas: found keywest-i2c-bus, checking if tas chip is on it
snd-aoa-codec-tas: created and attached tas instance
snd-aoa-codec-tas: found keywest-i2c-bus, checking if tas chip is on it
snd-aoa-codec-tas: created and attached tas instance
snd: Unknown layout ID 0x44
i2sbus: mapped i2s control registers
i2sbus: control register contents:
i2sbus:    fcr0 = 0x8000056
i2sbus:    cell_control = 0x5b43831a
i2sbus:    fcr2 = 0xe7008000
i2sbus:    fcr3 = 0x72009607
i2sbus:    clock_control = 0x0
i2sbus: found i2s controller
snd-aoa-fabric-layout: found bus with layout 68 (using)
snd-aoa: fabric didn't like codec tas
snd-aoa: fabric didn't like codec tas
snd-aoa-codec-onyx: found pcm3052
snd-aoa-fabric-layout: platform-onyx-codec-ref doesn't match!
snd-aoa: fabric didn't like codec onyx
snd-aoa-codec-onyx: created and attached onyx instance
snd-aoa-codec-onyx: found pcm3052
snd-aoa-fabric-layout: can use this codec
snd-aoa-codec-onyx: attached to onyx codec via i2c
snd-aoa-codec-onyx: created and attached onyx instance
serial format: 0x41190000
dws: 0x2000200
i2sbus: found i2s controller
snd-aoa-fabric-layout: found bus with layout 69 (using)
snd-aoa-fabric-layout: platform-onyx-codec-ref doesn't match!
snd-aoa: fabric didn't like codec onyx
snd-aoa: fabric didn't like codec tas
snd-aoa: fabric didn't like codec tas
serial format: 0x41100000
dws: 0x0
all codec info:
        formats = 0x808
        rates = 0x7fe

For the record, there are two "layout-id" properties in my device tree,
as discussed in this patch:
http://patchwork.ozlabs.org/linuxppc/patch?id=4867

Ultimately, snd_aoa_codec_onyx seems to be the happy module. Only the
headphone jack was enabled; I had to use GNOME's "Volume Control" panel
applet to enable speakers or line out (both of which work).

However, volume control doesn't work at all, for both line-out and
headphone jacks. Should it?

Also, it would be helpful if the git tree were better publicized
somewhere (e.g. http://johannes.sipsolutions.net/). I had to dig through a LOT of mails to find the source.
	mkdir snd-aoa
	cd snd-aoa/
	git clone http://johannes.sipsolutions.net/snd-aoa.git/ 
	cd snd-aoa/ 
	make

-Hollis

P.S. Thanks for working on this Johannes!

  parent reply	other threads:[~2006-05-23  3:12 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-17 10:09 snd-aoa status update / automatic driver loading Johannes Berg
2006-05-17 18:57 ` Tony Vroon
2006-05-19 10:22   ` Johannes Berg
2006-05-20 23:56     ` Benjamin Herrenschmidt
2006-05-22  6:42       ` Johannes Berg
2006-05-23 22:15         ` Benjamin Herrenschmidt
2006-05-24  9:42           ` Johannes Berg
2006-05-25  8:00             ` Benjamin Herrenschmidt
2006-05-25  9:42               ` Johannes Berg
2006-05-26  1:30                 ` Benjamin Herrenschmidt
2006-05-17 19:53 ` Andreas Schwab
2006-05-18 10:14   ` Johannes Berg
2006-05-17 21:54 ` Wolfgang Pfeiffer
2006-05-17 22:19   ` Wolfgang Pfeiffer
2006-05-18 10:13     ` Johannes Berg
2006-05-18 18:17       ` Wolfgang Pfeiffer
2006-05-18 22:06         ` Andreas Schwab
2006-05-19 12:50         ` Johannes Berg
2006-05-19 14:40           ` Wolfgang Pfeiffer
2006-05-19 14:40             ` Johannes Berg
2006-05-17 22:30   ` Dean Hamstead
2006-05-18  0:28     ` Wolfgang Pfeiffer
2006-05-18  0:39       ` Dean Hamstead
2006-05-18  1:01   ` Wolfgang Pfeiffer
2006-05-18  1:08   ` Benjamin Herrenschmidt
2006-05-18  7:25 ` Eddy Petrişor
2006-05-18 10:23   ` Johannes Berg
2006-05-19 13:20     ` Paul Collins
2006-05-19 13:46       ` Johannes Berg
2006-05-19 14:40         ` Paul Collins
2006-05-19 14:49           ` Johannes Berg
2006-05-19 15:13             ` Paul Collins
2006-05-19 14:33       ` Andreas Schwab
2006-05-19 14:37         ` Johannes Berg
2006-05-23 15:41       ` Sjoerd Simons
2006-05-25  7:21         ` Eddy Petrişor
2006-05-25  7:21           ` Eddy Petrişor
2006-05-25  9:43           ` Johannes Berg
2006-05-25 17:44     ` Eddy Petrişor
2006-05-25 18:47       ` Johannes Berg
2006-05-18  8:56 ` Rene Rebe
2006-05-18 10:08   ` Johannes Berg
     [not found] ` <200605180002.01669.borge@arivene.net>
     [not found]   ` <20060518004141.GC1552@kunpuu.plessy.org>
2006-05-20 14:57     ` Benjamin Berg
2006-05-20 23:59       ` Benjamin Herrenschmidt
2006-05-23  3:11 ` Hollis Blanchard [this message]
2006-05-23 12:27   ` Johannes Berg
2006-05-23 14:46     ` Hollis Blanchard
2006-05-23 15:25       ` Hollis Blanchard
2006-05-24  9:41       ` Johannes Berg

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=20060522221138.683790c2@diesel \
    --to=hollis@penguinppc.org \
    --cc=debian-powerpc@lists.debian.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).