From: Johannes Berg <johannes@sipsolutions.net>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Takashi Iwai <tiwai@suse.de>, Lee Revell <rlrevell@joe-job.com>,
ALSA devel <alsa-devel@lists.sourceforge.net>
Subject: Re: ac3 in/out
Date: Thu, 23 Mar 2006 18:06:21 +0100 [thread overview]
Message-ID: <1143133582.8395.14.camel@localhost> (raw)
In-Reply-To: <1143063593.3823.21.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 970 bytes --]
On Thu, 2006-03-23 at 08:39 +1100, Benjamin Herrenschmidt wrote:
> > Ok that's what I figured. Well, it has to change if I shall be able to
> > write a driver for the digital output of above chip.
>
> Well, you can be sneaky in the meantime :) If you use small buffers and
> large dbdma command lists, you can have the dbdma command list skip the
> status data but that mean one output command per sample (or packet),
> fairly horribly inefficient if your ratio data/status is not high :)
I don't think so, since the user/channel status bits are interleaved
*bitwise* :)
Though there's another thing I don't yet understand. If you look at the
three datasheets of the topaz chips, you'll notice that one of them is a
receiver, one of them a transmitter, and the third a transceiver! Now I
really wonder wtf apple is doing with them.
But to find out that, I first need to write a topaz module that probes
which one of the chips it is :)
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 793 bytes --]
next prev parent reply other threads:[~2006-03-23 17:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 10:27 ac3 in/out Johannes Berg
2006-03-21 18:17 ` Lee Revell
2006-03-21 18:37 ` Takashi Iwai
2006-03-22 9:41 ` Johannes Berg
2006-03-22 10:43 ` Takashi Iwai
2006-03-22 10:54 ` Johannes Berg
2006-03-22 11:09 ` Takashi Iwai
2006-03-22 11:12 ` Johannes Berg
2006-03-22 21:39 ` Benjamin Herrenschmidt
2006-03-23 17:06 ` Johannes Berg [this message]
2006-03-22 0:20 ` James Courtier-Dutton
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=1143133582.8395.14.camel@localhost \
--to=johannes@sipsolutions.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=benh@kernel.crashing.org \
--cc=rlrevell@joe-job.com \
--cc=tiwai@suse.de \
/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