mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Jes Sorensen <jes@sunsite.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how to get virtual address from dma address
Date: Sun, 7 Oct 2001 12:13:26 +1000 (EST)	[thread overview]
Message-ID: <15295.47686.932418.81948@cargo.ozlabs.ibm.com> (raw)
In-Reply-To: <d3adz4u1gx.fsf@lxplus014.cern.ch>
In-Reply-To: <200110032244.f93MiI103485@localhost.localdomain> <d3n136tc48.fsf@lxplus014.cern.ch> <15294.47999.501719.858693@cargo.ozlabs.ibm.com> <20011006.013819.17864926.davem@redhat.com> <15294.63138.941581.771248@cargo.ozlabs.ibm.com> <d3adz4u1gx.fsf@lxplus014.cern.ch>

Jes Sorensen writes:

> I haven't looked at the ohci driver at all, however doesn't it return
> anything but the dma address? No index, no offset, no nothing? If
> thats the case, someone really needs to go visit the designers with a
> large bat ;-(

The OHCI hardware works with linked lists of transfer descriptors,
using bus addresses for the pointers of course.  When a transfer
descriptor is completed, it gets linked onto a done-list by the
hardware (on to the front of the list, so you get the completed
descriptors in reverse order).

There is no way to predict the completion order in general because you
can have transfers in progress to several different devices, and to
several endpoints on each device, at the same time, which can each
supply or accept data at different rates.

I don't think the OHCI designers considered the possibility that it
might be less than straightforward for the CPU to access some memory
given its bus address.  And I would have a hard time arguing against
someone who claimed that a platform where that was difficult was
just terminally broken. :)

Paul.

  parent reply	other threads:[~2001-10-07  2:14 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1002355920.6872.linux-kernel2news@redhat.com>
2001-10-03 22:44 ` James Bottomley
2001-10-04  0:24   ` David S. Miller
2001-10-04 10:11     ` BALBIR SINGH
2001-10-04 11:16     ` David S. Miller
2001-10-04 15:37     ` James Bottomley
2001-10-05 14:06   ` Jes Sorensen
2001-10-06  8:38     ` David S. Miller
2001-10-06 18:19       ` Pete Zaitcev
2001-10-06 18:04     ` Pete Zaitcev
2001-10-06  8:06   ` Paul Mackerras
2001-10-06 12:18     ` Paul Mackerras
2001-10-06 14:45       ` James Bottomley
2001-10-06 16:51         ` Gérard Roudier
2001-10-06 17:23       ` Jes Sorensen
2001-10-07  7:21         ` Gérard Roudier
2001-10-07 16:23           ` James Bottomley
2001-10-07 18:24             ` Gérard Roudier
2001-10-07 23:02               ` James Bottomley
2001-10-08 21:06                 ` Gérard Roudier
2001-10-07  2:13       ` Paul Mackerras [this message]
2001-10-07 17:40         ` Jes Sorensen
     [not found] <Pine.LNX.4.21.0110031525370.14852-100000@pogo.esscom.com>
2001-10-03 21:48 ` Linux Bigot
2001-10-03 22:03   ` Ben Collins
2001-10-05 14:04   ` Jes Sorensen
2001-10-03 21:30 Manfred Spraul
  -- strict thread matches above, loose matches on Subject: below --
2001-10-03 16:37 Linux Bigot
2001-10-03 19:32 ` Ben Collins
2001-10-03 21:11   ` Linux Bigot
2001-10-03 21:23     ` Ben Collins
2001-10-03 14:11 Linux Bigot
2001-10-03 15:25 ` Jes Sorensen

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=15295.47686.932418.81948@cargo.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=jes@sunsite.dk \
    --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

all inboxes | Powered by JetHome®