public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes@sunsite.dk>
To: "MEHTA,HIREN (A-SanJose,ex1)" <hiren_mehta@agilent.com>
Cc: "'David S. Miller'" <davem@redhat.com>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: (reposting) how to get DMA'able memory within 4GB on 64-bit m achi ne
Date: 28 Jun 2001 21:41:22 +0200	[thread overview]
Message-ID: <d33d8kbdel.fsf@lxplus015.cern.ch> (raw)
In-Reply-To: <FEEBE78C8360D411ACFD00D0B7477971880AD5@xsj02.sjs.agilent.com>
In-Reply-To: "MEHTA,HIREN's message of "Thu, 28 Jun 2001 10:20:46 -0600"

>>>>> "Hiren" == MEHTA,HIREN (A-SanJose,ex1) <hiren_mehta@agilent.com> writes:

Hiren> Then why do we have 64-bit dma_addr_t on ia64 ?  -hiren

Because on ia64 you will get back a 64 bit pointer if you use
pci_set_dma_mask() to set a 64 bit mask before calling the pci
functions in question.

Jes

  reply	other threads:[~2001-06-28 19:42 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-28 16:20 (reposting) how to get DMA'able memory within 4GB on 64-bit m achi ne MEHTA,HIREN (A-SanJose,ex1)
2001-06-28 19:41 ` Jes Sorensen [this message]
2001-06-28 22:01   ` David S. Miller
2001-06-28 22:20     ` Jes Sorensen
2001-06-28 22:27       ` David S. Miller
2001-06-28 22:28       ` Alan Cox
2001-07-02  8:09         ` Jens Axboe
2001-06-28 22:24     ` Ben LaHaise
2001-06-28 22:29       ` David S. Miller
2001-06-28 22:31         ` Ben LaHaise
2001-06-28 22:38           ` David S. Miller
2001-06-28 22:45             ` Ben LaHaise
2001-06-28 22:48               ` David S. Miller
2001-06-28 22:48             ` (reposting) how to get DMA'able memory within 4GB on 64-bit m Alan Cox
2001-06-28 22:55             ` (reposting) how to get DMA'able memory within 4GB on 64-bit m achi ne Jes Sorensen
2001-06-29  9:16               ` David S. Miller
2001-06-29  9:56                 ` Alan Cox
2001-06-29 20:37                   ` David S. Miller
2001-07-05 21:06                     ` Jes Sorensen
2001-07-05 23:47                       ` David S. Miller
2001-07-05 23:50                         ` Ben LaHaise
2001-07-06 13:31                         ` Jes Sorensen
2001-07-06 23:46                           ` David S. Miller
2001-07-07  3:58                             ` Ben LaHaise
2001-07-07  5:35                               ` David S. Miller
2001-07-07 12:06                                 ` (reposting) how to get DMA'able memory within 4GB on 64-bit m Alan Cox
2001-07-07 12:17                                   ` Jeff Garzik
2001-07-07 12:21                                     ` Alan Cox
2001-07-07 13:00                                       ` David S. Miller
2001-07-11 19:16                                         ` Jes Sorensen
2001-07-11 21:54                                           ` Chris Wedgwood
2001-07-11 23:17                                             ` David S. Miller
2001-07-11 23:07                                           ` David S. Miller
2001-06-28 22:40           ` Alan Cox
2001-07-02  8:09       ` (reposting) how to get DMA'able memory within 4GB on 64-bit m achi ne Jens Axboe
2001-06-28 21:45 ` David S. Miller

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=d33d8kbdel.fsf@lxplus015.cern.ch \
    --to=jes@sunsite.dk \
    --cc=davem@redhat.com \
    --cc=hiren_mehta@agilent.com \
    --cc=linux-kernel@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