From: Takashi Iwai <tiwai@suse.de>
To: Meelis Roos <mroos@linux.ee>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
sparclinux@vger.kernel.org
Subject: Re: ALSA & missing dma_*_coherent on sparc32
Date: Thu, 26 Jul 2007 13:50:39 +0200 [thread overview]
Message-ID: <s5h7ionv0xc.wl%tiwai@suse.de> (raw)
In-Reply-To: <Pine.SOC.4.64.0707261317001.20971@math.ut.ee>
At Thu, 26 Jul 2007 13:21:01 +0300 (EEST),
Meelis Roos wrote:
>
> Tried to compile current 2.6.23-rc1+git on sparc32, along with sparc
> ALSA drivers as usual. But now the compilation is broken because of
> missing dma_*_coherent on sparc32. ISTR this got chenged recently on
> sparc32...
>
> ERROR: "dma_free_coherent" [sound/core/snd-page-alloc.ko] undefined!
> ERROR: "dma_alloc_coherent" [sound/core/snd-page-alloc.ko] undefined!
Could you show .config? Does it have CONFIG_HAS_DMA?
Takashi
next prev parent reply other threads:[~2007-07-26 11:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 10:21 ALSA & missing dma_*_coherent on sparc32 Meelis Roos
2007-07-26 11:50 ` Takashi Iwai [this message]
2007-07-26 12:02 ` Meelis Roos
2007-07-26 12:15 ` Takashi Iwai
2007-07-26 12:58 ` Sam Ravnborg
2007-07-26 13:04 ` Takashi Iwai
2007-07-27 9:58 ` Meelis Roos
2007-07-27 10:33 ` 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=s5h7ionv0xc.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=sparclinux@vger.kernel.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