public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@convergence.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: arjanv@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: 2.6.1-mm4: ALSA es1968 DMA alloc problem
Date: Tue, 20 Jan 2004 02:17:20 +0100	[thread overview]
Message-ID: <20040120011720.GA1248@convergence.de> (raw)
In-Reply-To: <s5hhdyru84m.wl@alsa2.suse.de>

On Mon, Jan 19, 2004 at 07:05:13PM +0100, Takashi Iwai wrote:
> At Mon, 19 Jan 2004 18:14:12 +0100,
> I wrote:
> > 
> > hmm, can calling pci_set_consistent_dma_mask() after
> > pci_set_dma_mask() fail?  then we need to fix
> > Documentation/DMA-mapping.txt, too.
> 
> well, anyway, the attached is one with checks of both returns.

The patch did not apply cleanly because it is against a newer
core/memalloc.c than the one in 2.6.1-mm4 (rev 1.19 vs. 1.20).
I fetched memalloc.c rev1.20 from ALSA CVS and applied the
patch on top of that: My es1968 soundcard works.

(To make sure the whole problem was not just caused by an
out-of-date memalloc.c in 2.6.1-mm4 I also tried just
the updated memalloc.c without your patch, but this did
not cure the "DMA buffer beyond 256MB" problem.)

Johannes

      reply	other threads:[~2004-01-20  1:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-17 16:10 2.6.1-mm4: ALSA es1968 DMA alloc problem Johannes Stezenbach
2004-01-19 16:29 ` Takashi Iwai
2004-01-19 16:43   ` Arjan van de Ven
2004-01-19 16:56     ` Takashi Iwai
2004-01-19 17:05   ` Arjan van de Ven
2004-01-19 17:14     ` Takashi Iwai
2004-01-19 18:05       ` Takashi Iwai
2004-01-20  1:17         ` Johannes Stezenbach [this message]

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=20040120011720.GA1248@convergence.de \
    --to=js@convergence.de \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@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