From: "David S. Miller" <davem@redhat.com>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] Re: [patch] support 64 bit pci_alloc_consistent
Date: Sun, 18 May 2003 09:35:33 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705931@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590723705928@msgid-missing>
From: Arjan van de Ven <arjanv@redhat.com>
Date: 18 May 2003 11:29:02 +0200
#define PCI_DMA_64BIT 0xffffffffffffffffULL
#define PCI_DMA_32BIT 0xffffffffULL
void pci_set_dma_capabilities(device,
u64 streaming_mask, u64 persistent_mask);
u64 pci_get_effective_streaming_mask(device);
u64 pci_get_effective_persistent_mask(device);
if for some reason the architecture PCI code needs or wants to reduce
the DMA mask
WHile logically you are correct, the probing code is going to
look basically identical.
Instead of frobbing around with pci_set_dma() calls, you're going
to be frobbing around with pci_get_effective*() calls and branching
based upon that.
I really see no value in this. Both are effectively equivalent
and the present setup has the advantage that it has existed for
some time and driver authors (at least some :-) know how to use
it already.
next prev parent reply other threads:[~2003-05-18 9:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-18 5:46 [Linux-ia64] Re: [patch] support 64 bit pci_alloc_consistent David S. Miller
2003-05-18 6:00 ` Andre Hedrick
2003-05-18 9:29 ` Arjan van de Ven
2003-05-18 9:35 ` David S. Miller [this message]
2003-05-18 9:43 ` Arjan van de Ven
2003-05-18 14:17 ` James Bottomley
2003-05-18 14:21 ` Arjan van de Ven
2003-05-18 14:28 ` James Bottomley
2003-05-18 17:22 ` Grant Grundler
2003-05-18 17:49 ` James Bottomley
2003-05-18 20:17 ` Grant Grundler
2003-05-18 21:26 ` James Bottomley
2003-05-19 16:26 ` Grant Grundler
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=marc-linux-ia64-105590723705931@msgid-missing \
--to=davem@redhat.com \
--cc=linux-ia64@vger.kernel.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