From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linus Torvalds <torvalds@osdl.org>,
Greg Kroah-Hartman <greg@kroah.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: dmapool (was: Re: Linux 2.6.3-rc2)
Date: Tue, 10 Feb 2004 14:47:19 +0000 [thread overview]
Message-ID: <20040210144719.B23310@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.GSO.4.58.0402101531240.2261@waterleaf.sonytel.be>; from geert@linux-m68k.org on Tue, Feb 10, 2004 at 03:32:47PM +0100
On Tue, Feb 10, 2004 at 03:32:47PM +0100, Geert Uytterhoeven wrote:
> On Tue, 10 Feb 2004, Geert Uytterhoeven wrote:
> > The dmapool code makes dma_{alloc,free}_coherent() a requirement for all
> > platforms, breaking platforms that don't have it (e.g. m68k, and from a quick
> > browse sparc and sparc64 probably, too).
> >
> > May not be that nice for a release candidate in a stable series...
>
> This patch seems to fix the problem (all offending platforms include
> <asm/generic.h> if CONFIG_PCI only):
Please don't - that breaks ARM. Part of the whole point of dmapool is
that it provides a generic DMA pool implementation, especially for
non-PCI USB devices.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-02-10 14:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 3:17 Linux 2.6.3-rc2 Linus Torvalds
2004-02-10 3:53 ` Misshielle Wong
2004-02-10 7:16 ` Jeffrey E. Hundstad
2004-02-10 12:59 ` Geert Uytterhoeven
2004-02-10 14:58 ` Bartlomiej Zolnierkiewicz
2004-02-10 15:18 ` Geert Uytterhoeven
2004-02-10 16:17 ` Bartlomiej Zolnierkiewicz
2004-02-10 17:28 ` Geert Uytterhoeven
2004-02-10 13:31 ` dmapool (was: Re: Linux 2.6.3-rc2) Geert Uytterhoeven
2004-02-10 14:32 ` Geert Uytterhoeven
2004-02-10 14:41 ` Kernel Fault 2.4.20 Ananda Bhattacharya
2004-02-10 14:47 ` Arjan van de Ven
2004-02-10 14:47 ` Russell King [this message]
2004-02-10 14:57 ` dmapool (was: Re: Linux 2.6.3-rc2) Geert Uytterhoeven
2004-02-10 14:55 ` Christoph Hellwig
2004-02-10 16:23 ` Greg KH
2004-02-10 16:29 ` Geert Uytterhoeven
2004-02-10 18:14 ` David S. Miller
2004-02-12 9:52 ` Geert Uytterhoeven
2004-02-12 10:25 ` Gerd Knorr
2004-02-13 15:24 ` Geert Uytterhoeven
2004-02-13 21:27 ` Roman Zippel
2004-02-10 17:00 ` Linux 2.6.3-rc2 (compile stats) John Cherry
-- strict thread matches above, loose matches on Subject: below --
2004-02-13 20:23 dmapool (was: Re: Linux 2.6.3-rc2) David Brownell
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=20040210144719.B23310@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=geert@linux-m68k.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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