From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Marc Zyngier <mzyngier@freesurf.fr>
Cc: rth@twiddle.net, linux-kernel@vger.kernel.org
Subject: Re: [Patch] DMA mapping API for Alpha
Date: Tue, 29 Apr 2003 16:23:22 +0400 [thread overview]
Message-ID: <20030429162322.B5767@jurassic.park.msu.ru> (raw)
In-Reply-To: <wrpvfwx5xcq.fsf@hina.wild-wind.fr.eu.org>; from mzyngier@freesurf.fr on Tue, Apr 29, 2003 at 01:58:29PM +0200
On Tue, Apr 29, 2003 at 01:58:29PM +0200, Marc Zyngier wrote:
> That's exactly what I wanted to avoid : It we feed NULL (for a non PCI
> device) to pci_map_single (for example), we limit the max DMA address
> to 24 bits, and this is quite bad for an EISA device, which is 32 bits
> capable.
Agreed, but what if your EISA-PCI bridge has only 30 address lines wired
to PCI? Yes, we can check this for EISA device because it has *real*
PCI parent (thanks, Marc :-), but what about ISA/legacy/whatever drivers?
I doubt that all of them bother to set dma_mask pointer (so you can have
an oops there).
Ivan.
next prev parent reply other threads:[~2003-04-29 12:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-28 18:38 Marc Zyngier
2003-04-28 18:49 ` Jeff Garzik
2003-04-28 18:52 ` Marc Zyngier
2003-04-28 22:20 ` Alan Cox
2003-04-29 6:59 ` Christoph Hellwig
2003-04-29 11:05 ` Ivan Kokshaysky
2003-04-29 11:20 ` Christoph Hellwig
2003-04-29 12:08 ` Ivan Kokshaysky
2003-04-29 12:32 ` Christoph Hellwig
2003-04-29 12:59 ` Ivan Kokshaysky
2003-04-29 11:58 ` Marc Zyngier
2003-04-29 12:23 ` Ivan Kokshaysky [this message]
2003-04-29 12:37 ` Marc Zyngier
2003-04-29 12:41 ` Christoph Hellwig
2003-04-29 20:08 ` Ivan Kokshaysky
2003-05-01 10:56 ` David S. Miller
2003-04-30 12:07 ` Maciej W. Rozycki
2003-04-30 14:12 ` Jeff Garzik
2003-04-30 14:18 ` Marc Zyngier
2003-04-30 19:25 ` Maciej W. Rozycki
2003-04-29 20:22 James Bottomley
2003-04-29 20:46 ` Ivan Kokshaysky
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=20030429162322.B5767@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=mzyngier@freesurf.fr \
--cc=rth@twiddle.net \
/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
all inboxes | Powered by JetHome®