From: Paul Mundt <lethal@linux-sh.org>
To: Adrian McMenamin <adrian@mcmen.demon.co.uk>
Cc: Alsa-devel <alsa-devel@lists.sourceforge.net>,
linux-sh <linuxsh-dev@lists.sourceforge.net>
Subject: Re: [PATCH] ALSA driver for Yamaa AICA on Sega Dreamcast
Date: Mon, 17 Apr 2006 12:52:26 +0300 [thread overview]
Message-ID: <20060417095226.GA8910@linux-sh.org> (raw)
In-Reply-To: <1145267096.9238.6.camel@localhost.localdomain>
Removing l-k from CC, since it's not likely anyone cares.
On Mon, Apr 17, 2006 at 10:44:56AM +0100, Adrian McMenamin wrote:
> As I wrote last week dma_wait_for_completion won't hack G2 DMA:
>
> get_residue never returns 0 for G2 DMA. When the dma is complete
> get_residue returns the size of the total transfer. Therefore I've no
> choice but to write my own handler (spinlocks question aside).
Then the G2 DMA ->get_residue() op needs to be fixed, as it's broken.
Don't work against the subsystem, it knows what it's doing.
You might be better off getting rid of it entirely and seeing about
getting the TEI working, you can check for completion and wake up
accordingly in this case, which is what you ideally want anyways. The
busy-loop in the generic dma_wait_for_completion() is a stupid hack for
people that haven't fixed up their TEI handling yet, it's not intended
for widespread use..
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
next prev parent reply other threads:[~2006-04-17 9:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-17 0:13 [PATCH] ALSA driver for Yamaa AICA on Sega Dreamcast Adrian McMenamin
2006-04-17 1:29 ` Paul Mundt
2006-04-17 1:29 ` [linuxsh-dev] " Paul Mundt
2006-04-17 9:44 ` [Alsa-devel] " Adrian McMenamin
2006-04-17 9:52 ` Paul Mundt [this message]
2006-04-17 10:04 ` Paul Mundt
2006-04-17 11:51 ` [linuxsh-dev] " Adrian McMenamin
2006-04-17 20:40 ` Adrian McMenamin
2006-04-17 20:00 ` Adrian McMenamin
2006-04-17 20:00 ` [linuxsh-dev] " Adrian McMenamin
2006-04-17 21:47 ` [Alsa-devel] " Lee Revell
2006-04-17 22:05 ` Christoph Hellwig
2006-04-17 22:15 ` Lee Revell
2006-04-18 10:17 ` Takashi Iwai
2006-04-18 10:17 ` [Alsa-devel] " Takashi Iwai
2006-04-18 11:52 ` Christoph Hellwig
2006-04-18 11:52 ` [Alsa-devel] " Christoph Hellwig
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=20060417095226.GA8910@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=adrian@mcmen.demon.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linuxsh-dev@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.