All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: wuzhangjin@gmail.com
Cc: linux-mips@linux-mips.org, alsa-devel@alsa-project.org,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	linux-kernel@vger.kernel.org, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH] MIPS: Fixups of ALSA memory maps
Date: Mon, 23 Nov 2009 09:56:39 +0100	[thread overview]
Message-ID: <s5h3a45aabc.wl%tiwai@suse.de> (raw)
In-Reply-To: <1258806701.5752.8.camel@falcon.domain.org>

At Sat, 21 Nov 2009 20:31:41 +0800,
Wu Zhangjin wrote:
> 
> On Wed, 2009-11-18 at 18:47 +0100, Takashi Iwai wrote:
> [...]
> > 
> > Well, we haven't reached the consensus.  The discussion faded away
> > somehow mainly because I had too little time to update and ping people
> > again.
> > 
> > In Tokyo, I talked with some guys regarding this.  Ben agreed to take
> > this approach for ppc, and David said that he doesn't mind for sparc
> > part.   Fujita-san mentioned it's no big problem to add one op from
> > the generic dma_ops.
> > 
> > So, maybe somehow need to convince James in the end (and ask Paul to
> > check SH part, too), then it'll be all up... theoretically :)
> > 
> > Anyway, I'm going to raise the discussion again on linux-arch.
> > I'm afraid it's a bit too late game for 2.6.33, but starting now is
> > better than too late again.
> 
> Hi, Takashi Iwai
> 
> Before the API stuff going into the mainline(2.6.33), can we apply this
> "[PATCH] MIPS: Fixups of ALSA memory maps"(This is the minimal
> necessares) as a current fixup. and then we will not get a broken sound
> support for MIPS, and also the support to the latest Loongson2F family
> machines will benefit from it.
> 
> and Ralf, what about your suggestion?

The question is whether this hack can be safely added for all MIPS
platforms just by checking kconfig.  I had an impression that rather
many things have to be checked in the runtime.

As I have really little clue about MIPS architecture, I'd like let
MIPS guys decide about it...


thanks,

Takashi

WARNING: multiple messages have this Message-ID (diff)
From: Takashi Iwai <tiwai@suse.de>
To: wuzhangjin@gmail.com
Cc: Ralf Baechle <ralf@linux-mips.org>,
	Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
	Jaroslav Kysela <perex@perex.cz>,
	alsa-devel@alsa-project.org, linux-mips@linux-mips.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: Fixups of ALSA memory maps
Date: Mon, 23 Nov 2009 09:56:39 +0100	[thread overview]
Message-ID: <s5h3a45aabc.wl%tiwai@suse.de> (raw)
In-Reply-To: <1258806701.5752.8.camel@falcon.domain.org>

At Sat, 21 Nov 2009 20:31:41 +0800,
Wu Zhangjin wrote:
> 
> On Wed, 2009-11-18 at 18:47 +0100, Takashi Iwai wrote:
> [...]
> > 
> > Well, we haven't reached the consensus.  The discussion faded away
> > somehow mainly because I had too little time to update and ping people
> > again.
> > 
> > In Tokyo, I talked with some guys regarding this.  Ben agreed to take
> > this approach for ppc, and David said that he doesn't mind for sparc
> > part.   Fujita-san mentioned it's no big problem to add one op from
> > the generic dma_ops.
> > 
> > So, maybe somehow need to convince James in the end (and ask Paul to
> > check SH part, too), then it'll be all up... theoretically :)
> > 
> > Anyway, I'm going to raise the discussion again on linux-arch.
> > I'm afraid it's a bit too late game for 2.6.33, but starting now is
> > better than too late again.
> 
> Hi, Takashi Iwai
> 
> Before the API stuff going into the mainline(2.6.33), can we apply this
> "[PATCH] MIPS: Fixups of ALSA memory maps"(This is the minimal
> necessares) as a current fixup. and then we will not get a broken sound
> support for MIPS, and also the support to the latest Loongson2F family
> machines will benefit from it.
> 
> and Ralf, what about your suggestion?

The question is whether this hack can be safely added for all MIPS
platforms just by checking kconfig.  I had an impression that rather
many things have to be checked in the runtime.

As I have really little clue about MIPS architecture, I'd like let
MIPS guys decide about it...


thanks,

Takashi

  reply	other threads:[~2009-11-23  8:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 16:48 [PATCH] MIPS: Fixups of ALSA memory maps Wu Zhangjin
2009-11-16 17:06 ` Ralf Baechle
2009-11-16 17:06   ` Ralf Baechle
2009-11-16 17:14   ` Takashi Iwai
2009-11-16 17:14     ` Takashi Iwai
2009-11-17 13:50     ` Ralf Baechle
2009-11-17 13:50       ` Ralf Baechle
2009-11-16 17:12 ` Takashi Iwai
2009-11-16 17:12   ` Takashi Iwai
2009-11-16 17:43   ` Ralf Baechle
2009-11-16 17:43     ` Ralf Baechle
2009-11-17  9:29     ` Takashi Iwai
2009-11-17  9:29       ` Takashi Iwai
2009-11-18 14:20       ` Ralf Baechle
2009-11-18 14:20         ` Ralf Baechle
2009-11-18 17:47         ` Takashi Iwai
2009-11-18 17:47           ` Takashi Iwai
2009-11-21 12:31           ` Wu Zhangjin
2009-11-23  8:56             ` Takashi Iwai [this message]
2009-11-23  8:56               ` Takashi Iwai
2009-11-23 12:36               ` Ralf Baechle
2009-11-23 12:36                 ` Ralf Baechle
2009-11-26 14:51                 ` Takashi Iwai
2009-11-26 14:51                   ` 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=s5h3a45aabc.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.org \
    --cc=tsbogend@alpha.franken.de \
    --cc=wuzhangjin@gmail.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 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.