From: Jes Sorensen <jes@wildopensource.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
willy@debian.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] move dma_consistent_dma_mask to the generic device
Date: 03 Mar 2004 10:29:40 -0500 [thread overview]
Message-ID: <yq0llmit0d7.fsf@wildopensource.com> (raw)
In-Reply-To: <1077759287.14081.24.camel@mulgrave>
>>>>> "James" == James Bottomley <James.Bottomley@steeleye.com> writes:
James> pci_dev.consistent_dma_mask was introduced to get around
James> problems in the IA64 Altix machine.
James> Now, we have a use for it in x86: the aacraid needs coherent
James> memory in a 31 bit address range (2GB). Unfortunately, x86 is
James> converted to the dma model, so it can't see the pci_dev by the
James> time coherent memory is allocated.
James,
Could you add this one to your patchset, it fixes the sn2 code to work
with the new location of the mask.
Thanks,
Jes
--- arch/ia64/sn/io/machvec/pci_dma.c~ Wed Mar 3 06:47:36 2004
+++ arch/ia64/sn/io/machvec/pci_dma.c Wed Mar 3 07:23:34 2004
@@ -152,7 +152,7 @@
* pcibr_dmatrans_addr ignores a missing PCIIO_DMA_A64 flag on
* PCI-X buses.
*/
- if (hwdev->consistent_dma_mask == ~0UL)
+ if (hwdev->dev.coherent_dma_mask == ~0UL)
*dma_handle = pcibr_dmatrans_addr(vhdl, NULL, phys_addr, size,
PCIIO_DMA_CMD | PCIIO_DMA_A64);
else {
@@ -169,7 +169,7 @@
}
}
- if (!*dma_handle || *dma_handle > hwdev->consistent_dma_mask) {
+ if (!*dma_handle || *dma_handle > hwdev->dev.coherent_dma_mask) {
if (dma_map) {
pcibr_dmamap_done(dma_map);
pcibr_dmamap_free(dma_map);
prev parent reply other threads:[~2004-03-03 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-26 1:34 [PATCH] move dma_consistent_dma_mask to the generic device James Bottomley
2004-02-26 2:06 ` Andrew Morton
2004-02-26 2:55 ` James Bottomley
2004-03-03 15:29 ` Jes Sorensen [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=yq0llmit0d7.fsf@wildopensource.com \
--to=jes@wildopensource.com \
--cc=James.Bottomley@steeleye.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=willy@debian.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