From: "Petr Vandrovec" <VANDROVE@vc.cvut.cz>
To: Russell King <rmk@arm.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Physical memory addresses/PCI memory addresses/io_remap
Date: Thu, 14 Dec 2000 17:56:54 MET-1 [thread overview]
Message-ID: <FA894952830@vcnet.vc.cvut.cz> (raw)
On 14 Dec 00 at 15:16, Russell King wrote:
> virtual space - address space that the kernel runs in
> physical space - address space that the CPU sits in
> PCI memory space - memory address space that the PCI peripherals sit in
== bus address...
>
> Many, if not all ARM architectures have physical address 0 different from
> PCI memory address 0.
>
> According to include/linux/fb.h, fb drivers should place a physical address
> into "fix.smem_start" and "fix.mmio_start", which can then be passed to
> io_remap_page_range.
>
> 1. Should pci_resource_start be returning the PCI memory space address or
> a physical memory space address?
I believe that pci_resource_start() should return physical address, not
bus one. It already happens on PReP.
> 3. Do we need a macro to convert PCI memory space addresses to physical
> memory space addresses?
No. You need PCI memory space address only for busmastering transfers.
And for PCI DMA there is specialized API... Currently all bus -> physical
mapping should be hidden in platform specific PCI code.
> 4. What does this mean for ioremap? (currently, on ARM, ioremap takes
> PCI memory space addresses, not a physical memory address, which makes
> the physmap MTD driver technically broken).
And ioremap() should take physical address, returning virtual one.
Best regards,
Petr Vandrovec
vandrove@vc.cvut.cz
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-14 17:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-14 17:56 Petr Vandrovec [this message]
2000-12-14 18:37 ` Physical memory addresses/PCI memory addresses/io_remap Alan Cox
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=FA894952830@vcnet.vc.cvut.cz \
--to=vandrove@vc.cvut.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.