From: David Mosberger <davidm@napali.hpl.hp.com>
To: Dave Olien <dmo@osdl.org>
Cc: davidm@hpl.hp.com, "David S. Miller" <davem@redhat.com>,
phillips@arcor.de, davidm@napali.hpl.hp.com, axboe@suse.de,
_deepfire@mail.ru, linux-kernel@vger.kernel.org
Subject: Re: DAC960 in 2.5.38, with new changes
Date: Tue, 24 Sep 2002 12:12:29 -0700 [thread overview]
Message-ID: <15760.47389.969846.226538@napali.hpl.hp.com> (raw)
In-Reply-To: <20020924112519.D17658@acpi.pdx.osdl.net>
>>>>> On Tue, 24 Sep 2002 11:25:19 -0700, Dave Olien <dmo@osdl.org> said:
Dave> Ok, thanks for explaining!
Dave> On Tue, Sep 24, 2002 at 11:21:45AM -0700, David Mosberger wrote:
>> >>>>> On Tue, 24 Sep 2002 10:28:43 -0700, Dave Olien <dmo@osdl.org> said:
>>
>> The idea is to do something along these lines:
>>
>> o Use PCA DMA interface for managing all DMA buffers.
>>
>> o If sizeof(dma_addr_t) > 4, turn on DAC mode and call
>> pci_set_dma_mask(dev, MAX_ADDR), where MAX_ADDR is the maximum
>> address that can be reached by the controller (i.e.,
>> 0xffffffffffffffff for a truly 64-bit-capable PCI controller).
>>
>> This way, everything should work out correctly and with good
>> performance on all imaginable platforms (ia64 with and without
>> hardware I/O TLB, plain x86, x86 with >4GB RAM, SPARC64 with 32-bit
>> dma_addr_t, etc.).
Come to think of it, the following refinement may be preferable:
o Use PCA DMA interface for managing all DMA buffers.
o limit = min(~(dma_addr_t) 0, MAX_ADDR), where MAX_ADDR is the maximum
address that can be reached by the controller (i.e.,
0xffffffffffffffff for a truly 64-bit-capable PCI controller).
o Call pci_set_dma_mask(dev, limit).
o If limit > 0xffffffff, turn on DAC mode.
This "algorithm" should be correct for all PCI controllers.
--david
next prev parent reply other threads:[~2002-09-24 19:07 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-23 19:04 Dave Olien
2002-09-23 19:19 ` David Mosberger
2002-09-23 20:40 ` David S. Miller
2002-09-23 20:53 ` David Mosberger
2002-09-23 20:57 ` David S. Miller
2002-09-23 21:24 ` David Mosberger
2002-09-23 21:17 ` David S. Miller
2002-09-23 21:32 ` David Mosberger
2002-09-23 21:28 ` David S. Miller
2002-09-23 21:31 ` Daniel Phillips
2002-09-23 21:33 ` David Mosberger
2002-09-23 21:28 ` David S. Miller
2002-09-23 21:40 ` Daniel Phillips
2002-09-23 21:45 ` David Mosberger
2002-09-23 20:44 ` Daniel Phillips
2002-09-23 20:54 ` David S. Miller
2002-09-24 16:54 ` Dave Olien
2002-09-24 17:11 ` David Mosberger
2002-09-24 17:28 ` Dave Olien
2002-09-24 18:21 ` David Mosberger
2002-09-24 18:25 ` Dave Olien
2002-09-24 19:12 ` David Mosberger [this message]
2002-09-24 18:45 ` Dave Olien
2002-09-24 17:50 ` Daniel Phillips
2002-09-24 18:27 ` David Mosberger
2002-09-24 17:39 ` Daniel Phillips
2002-09-25 22:20 ` DAC960, documentation links Daniel Phillips
2002-09-25 22:23 ` Daniel Phillips
2002-09-26 0:02 ` Mr. James W. Laferriere
2002-09-26 16:13 ` DAC960 in 2.5.38, with new changes Alan Cox
2002-09-24 17:45 ` Daniel Phillips
2002-09-25 21:42 ` davide.rossetti
2002-09-23 20:39 ` Daniel Phillips
2002-09-23 21:41 ` Dave Olien
2002-09-23 21:53 ` Daniel Phillips
2002-09-23 22:03 ` Dave Olien
2002-09-23 22:22 ` Daniel Phillips
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=15760.47389.969846.226538@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=_deepfire@mail.ru \
--cc=axboe@suse.de \
--cc=davem@redhat.com \
--cc=davidm@hpl.hp.com \
--cc=dmo@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@arcor.de \
--subject='Re: DAC960 in 2.5.38, with new changes' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).