public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] 2.4.16-ia64-011128 is missing dma64_addr_t
Date: Tue, 04 Dec 2001 19:54:34 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590698805599@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590698805568@msgid-missing>

>>>>> On Tue, 4 Dec 2001 16:52:05 +0100, Christoph Hellwig <hch@caldera.de> said:

  Christoph> On Tue, Dec 04, 2001 at 07:49:07AM -0800, David Mosberger
  Christoph> wrote: IA64 should use instead of it's horrible iommu
  Christoph> emulation.
  >>  Huh?  pci_dac_*() does not help you here at all.  pci_dac_*() is
  >> only needed/useful for 64-bit platforms which use a dma_addr_t
  >> that is smaller than 64 bits.  And even then is it needed only
  >> for drivers that create tons of mappings.

  Christoph> pci_dac_*() is defined to operate on dma64_addr_t
  Christoph> independand on wether it actually is different on
  Christoph> dma_addr_t.

Yes, but pci_dac_*() is also specifically designed *not* to do any
remapping.  It must do direct translation between address spaces
(i.e., basically what used to be called bus_to_virt()/virt_to_bus()).
It works only for fully-64bit capable DMA engines.

  Christoph> Maybe it should have been named dmadac_addr_t instead..

Perhaps.

	--david


  parent reply	other threads:[~2001-12-04 19:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-02  3:56 [Linux-ia64] 2.4.16-ia64-011128 is missing dma64_addr_t Keith Owens
2001-12-03 18:23 ` Gérard Roudier
2001-12-03 19:34 ` David Mosberger
2001-12-03 21:29 ` David Mosberger
2001-12-04 17:01 ` Gérard Roudier
2001-12-04 18:15 ` Gérard Roudier
2001-12-04 19:38 ` Gérard Roudier
2001-12-04 19:54 ` David Mosberger
2001-12-04 19:54 ` David Mosberger [this message]
2001-12-04 19:54 ` David Mosberger
2001-12-04 19:55 ` David Mosberger
2001-12-04 19:56 ` David Mosberger
2001-12-04 21:42 ` 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=marc-linux-ia64-105590698805599@msgid-missing \
    --to=davidm@hpl.hp.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