public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Martin Frey" <frey@scs.ch>
To: "'Alexander Ehlert'" <alexander.ehlert@uni-tuebingen.de>,
	"'Richard B. Johnson'" <root@chaos.analogic.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: Right Semantics for ioremap, remap_page_range
Date: Wed, 18 Jul 2001 10:34:17 -0400	[thread overview]
Message-ID: <011e01c10f96$bb014c20$1b876ace@SCHLEPPDOWN> (raw)
In-Reply-To: <Pine.LNX.4.32.0107181445110.809-100000@frodo.sau98.de>

Hi,

>What I now do is ioremap_nocache and do writel's, readl's on it.
>For the mmap stuff, I just call remap_page_range with the physical
>address that I get from pci_resource_start(). Is that alright?
>I mean it's working for me now, thats most important :)
>
That does not work on an Alpha. The Alpha (at leat my DS20 and
ES40) is happy with result of ioremap feeded into remap_page_range,
or the real CPU physical address (pci_resource_start + 0x80000000000
on Tsunami chipset).
There is an io_remap_page_range, which does a
remap_page_range(virt_to_phys(ioremap(pci_resource_start()))) on
Alpha, but this does not work either.

There must be a portable way to export PCI memory space to user space,
since e.g. the X servers are using that.

Any hints?

Thanks & regards,

Martin

  reply	other threads:[~2001-07-18 14:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-18 11:36 Right Semantics for ioremap, remap_page_range Alexander Ehlert
2001-07-18 12:40 ` Richard B. Johnson
2001-07-18 12:52   ` Alexander Ehlert
2001-07-18 14:34     ` Martin Frey [this message]
     [not found] <mailman.995456342.9505.linux-kernel2news@redhat.com>
2001-07-18 19:16 ` Pete Zaitcev
     [not found] <mailman.995466971.12450.linux-kernel2news@redhat.com>
2001-07-18 19:19 ` Pete Zaitcev

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='011e01c10f96$bb014c20$1b876ace@SCHLEPPDOWN' \
    --to=frey@scs.ch \
    --cc=alexander.ehlert@uni-tuebingen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.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