The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: Meelis Roos <mroos@linux.ee>,
	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 14:58:34 +0200	[thread overview]
Message-ID: <20070726125834.GA4041@uranus.ravnborg.org> (raw)
In-Reply-To: <s5h6447uzrk.wl%tiwai@suse.de>

On Thu, Jul 26, 2007 at 02:15:43PM +0200, Takashi Iwai wrote:
> At Thu, 26 Jul 2007 15:02:51 +0300 (EEST),
> Meelis Roos wrote:
> > 
> > > > 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?
> > 
> > No, CONFIG_NO_DMA=y - and this was recently changed on sparc32 IIRC.
> 
> OK, then could you try the patch below?

Hi Takashi-san.

Can I ask you to introdue use of the -y syntax for composite objects.
This would simplify soucd/core/Makefile

The below would then become:
>  
> -snd-page-alloc-objs := memalloc.o sgbuf.o
> +snd-page-alloc-y := memalloc.o
> +snd-page-alloc-$(CONFIG_HAS_DMA) += sgbuf.o
>  
>  snd-rawmidi-objs  := rawmidi.o
>  snd-timer-objs    := timer.o

Ask if you have questions.

Thanks,
	Sam

  reply	other threads:[~2007-07-26 12:57 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
2007-07-26 12:02   ` Meelis Roos
2007-07-26 12:15     ` Takashi Iwai
2007-07-26 12:58       ` Sam Ravnborg [this message]
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=20070726125834.GA4041@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    --cc=sparclinux@vger.kernel.org \
    --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