From: Takashi Iwai <tiwai@suse.de>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-kernel@vger.kernel.org, tbm@cyrius.com,
t.sailer@alumni.ethz.ch, perex@suse.cz, ralf@linux-mips.org
Subject: Re: ALSA on MIPS platform
Date: Thu, 26 Jan 2006 17:02:53 +0100 [thread overview]
Message-ID: <s5hzmljt1si.wl%tiwai@suse.de> (raw)
In-Reply-To: <20060127.002925.25911749.anemo@mba.ocn.ne.jp>
At Fri, 27 Jan 2006 00:29:25 +0900 (JST),
Atsushi Nemoto wrote:
>
> >>>>> On Wed, 25 Jan 2006 20:03:13 +0100, Takashi Iwai <tiwai@suse.de> said:
>
> tiwai> The right fix is, IMO, to port dma_mmap_coherent() to all
> tiwai> archs. Currently, it's only on ARM.
>
> Thanks. Is this solve both issue #1 and #2 ?
Yes. In theory, dma_alloc_coherent() and dma_mmap_coherent() should
cover all the magic each arch requires.
> The most part of issue #1 will vanish if NEED_RESERVE_PAGES was
> defined, and currently only ARM define this. ARM defines
> NEED_RESERVE_PAGES because it has dma_mmap_coherent(), right?
Well, the whole page-reserve kludge should disappear anyway in near
future. Right now it's in the process.
The memory allocation stuff in ALSA is being largely rewritten on my
local tree, but it's not released yet. One reason is to wait for the
finish of page-reserve removals, and another reason is that I've had
little time to tidy them up :)
--
Takashi Iwai <tiwai@suse.de> ALSA Developer - www.alsa-project.org
next prev parent reply other threads:[~2006-01-26 15:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 14:50 ALSA on MIPS platform Atsushi Nemoto
2006-01-25 19:03 ` Takashi Iwai
2006-01-26 15:29 ` Atsushi Nemoto
2006-01-26 16:02 ` Takashi Iwai [this message]
2006-01-26 19:19 ` Hugh Dickins
2006-01-27 15:45 ` Atsushi Nemoto
2006-01-27 15:49 ` Martin Michlmayr
2006-01-27 16:01 ` Takashi Iwai
2006-01-27 15:57 ` Takashi Iwai
2006-01-30 9:56 ` Atsushi Nemoto
2006-01-30 10:18 ` Takashi Iwai
2006-01-30 10:38 ` Atsushi Nemoto
2006-01-30 12:25 ` Ralf Baechle
2006-01-30 15:46 ` Martin Michlmayr
2006-01-30 15:52 ` Takashi Iwai
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=s5hzmljt1si.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=anemo@mba.ocn.ne.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
--cc=ralf@linux-mips.org \
--cc=t.sailer@alumni.ethz.ch \
--cc=tbm@cyrius.com \
/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).