linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@netx4.com>
To: Roman Zippel <zippel@fh-brandenburg.de>
Cc: Ronald Wahl <rwa@peppercon.de>,
	Benjamin Herrenschmidt <bh40@calva.net>,
	linuxppc-dev@lists.linuxppc.org
Subject: Re: allocating uncachable memory
Date: Sun, 27 Aug 2000 15:46:02 -0400	[thread overview]
Message-ID: <39A96FFA.EF350293@embeddededge.com> (raw)
In-Reply-To: Pine.GSO.4.10.10008261825550.25785-100000@zeus.fh-brandenburg.de


Roman Zippel wrote:

> IMO the only portable solution would be a memremap (similiar to ioremap).

Coming up with a function name and actually implementing it are two
very different things......ioremap() should do the right thing.
There are also many other issues associated with the macros
bus_to_virt() and virt_to_bus() that are challenging.

> Sure?

Yes I am sure.  Bursting data over the bus is hell of a lot faster,
especially in this case where the PCI bridge can combine these into
a PCI burst transfer as well.


	-- Dan

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-08-27 19:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-23 13:50 allocating uncachable memory Ronald Wahl
2000-08-23 14:03 ` Benjamin Herrenschmidt
2000-08-23 17:37   ` Dan Malek
2000-08-24  7:42     ` Ronald Wahl
2000-08-25  7:12       ` Ronald Wahl
2000-08-25 17:39         ` Dan Malek
2000-08-26 16:34           ` Roman Zippel
2000-08-27 19:46             ` Dan Malek [this message]
2000-08-27 21:26               ` Roman Zippel
2000-08-27 22:52                 ` Dan Malek
2000-08-28 20:04                   ` Roman Zippel
2000-08-28 20:34                     ` Dan Malek
2000-08-28 21:33                       ` Roman Zippel
2000-08-28 12:05           ` Ronald Wahl
2000-08-28 15:25             ` Dan Malek
2000-08-29  7:29               ` Ronald Wahl
2000-08-23 14:11 ` Gabriel Paubert
2000-08-24  9:14   ` Ronald Wahl

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=39A96FFA.EF350293@embeddededge.com \
    --to=dan@netx4.com \
    --cc=bh40@calva.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=rwa@peppercon.de \
    --cc=zippel@fh-brandenburg.de \
    /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;
as well as URLs for NNTP newsgroup(s).