From: David Mosberger <davidm@hpl.hp.com>
To: Christoph Hellwig <hch@caldera.de>
Cc: "David S. Miller" <davem@redhat.com>,
davidm@hpl.hp.com, mmadore@turbolinux.com,
linux-ia64@linuxia64.org, linux-kernel@vger.kernel.org,
groudier@free.fr
Subject: Re: [Linux-ia64] Proper fix for sym53c8xx_2 driver and dma64_addr_t
Date: Wed, 6 Feb 2002 09:15:22 -0800 [thread overview]
Message-ID: <15457.25770.707397.595744@napali.hpl.hp.com> (raw)
In-Reply-To: <20020206181042.A11683@caldera.de>
In-Reply-To: <20020206092129.A8739@caldera.de> <20020206.002906.94555802.davem@redhat.com> <20020206093558.A9445@caldera.de> <20020206.004503.118628125.davem@redhat.com> <20020206181042.A11683@caldera.de>
>>>>> On Wed, 6 Feb 2002 18:10:42 +0100, Christoph Hellwig <hch@caldera.de> said:
Christoph> On Wed, Feb 06, 2002 at 12:45:03AM -0800, David S. Miller
Christoph> wrote:
>> It is not using the DMA apis correctly then, it should be using
>> dma_addr_t which may or may not be 64-bits on a given platform.
Christoph> When the sym2 driver is configured with
Christoph> SYM_CONF_DMA_ADDRESSING_MOD > 1 it uses DAC accessing and
Christoph> needs dma64_addr_t. It doesn't use it when using the
Christoph> default addressing mode.
The driver never uses the pci_dac* interface, hence it should not use
dma64_addr_t. If the driver needs a 64-bit wide type, u64 will do
fine.
--david
next prev parent reply other threads:[~2002-02-06 17:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C6043E5.D1F40E5D@turbolinux.com>
[not found] ` <20020205223804.A22012@caldera.de>
[not found] ` <15456.21030.840746.209377@napali.hpl.hp.com>
2002-02-06 8:21 ` Christoph Hellwig
2002-02-06 8:29 ` David S. Miller
2002-02-06 8:35 ` Christoph Hellwig
2002-02-06 8:45 ` David S. Miller
2002-02-05 21:23 ` Gérard Roudier
2002-02-06 17:10 ` Christoph Hellwig
2002-02-06 17:15 ` Christoph Hellwig
2002-02-06 17:15 ` David Mosberger [this message]
2002-02-05 21:34 ` Gérard Roudier
2002-02-07 2:09 ` David S. Miller
2002-02-06 21:38 ` Gérard Roudier
2002-02-06 16:54 ` David Mosberger
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=15457.25770.707397.595744@napali.hpl.hp.com \
--to=davidm@hpl.hp.com \
--cc=davem@redhat.com \
--cc=groudier@free.fr \
--cc=hch@caldera.de \
--cc=linux-ia64@linuxia64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmadore@turbolinux.com \
/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®