linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gerhard Pircher <gerhard_pircher@gmx.net>
Cc: Takashi Iwai <tiwai@suse.de>, linuxppc-dev@ozlabs.org
Subject: Re: ALSA fixes for non-coherent ppc32 again
Date: Mon, 22 Jun 2009 08:34:38 +1000	[thread overview]
Message-ID: <1245623678.16880.27.camel@pasglop> (raw)
In-Reply-To: <20090621181855.74980@gmx.net>

On Sun, 2009-06-21 at 20:18 +0200, Gerhard Pircher wrote:
> Hi,
> 
> Takashi Iwai posted patches to make ALSA work on non-coherent PPC32
> systems (almost exactly) a year ago. See here:
> http://www.nabble.com/-PATCH-0-3--ALSA-fixes-for-non-coherent-ppc32-to17980027.html#a17980027
> 
> As far as I can see these patches never went upstream. Where there any
> objections or did we just forget about them? It would be cool, if the
> patches could be merged now, as at least two platforms need this bugfix
> (namely Sam440 and AmigaOne).

I definitely forgot about those... But I'm fine with what Takashi did
for now, I can always make the powerpc helper for dma_mmap_coherent()
smarter later on if necessary.

Cheers,
Ben.

  reply	other threads:[~2009-06-21 22:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-21 18:18 ALSA fixes for non-coherent ppc32 again Gerhard Pircher
2009-06-21 22:34 ` Benjamin Herrenschmidt [this message]
2009-06-22  7:12   ` Takashi Iwai
2009-06-22  9:23     ` Gerhard Pircher
2009-06-23  8:55     ` Gerhard Pircher
2009-06-23 21:42       ` Gerhard Pircher
2009-06-24  8:46         ` Gerhard Pircher
2009-06-24  9:47           ` Takashi Iwai
2009-06-26 13:14             ` Gerhard Pircher
2009-07-08 14:14               ` Takashi Iwai
2009-07-08  3:01   ` Benjamin Herrenschmidt
2009-07-08 14:13     ` Takashi Iwai
2009-07-09 11:22       ` Gerhard Pircher

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=1245623678.16880.27.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=gerhard_pircher@gmx.net \
    --cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).