From: Oliver Korpilla <okorpil@fh-landshut.de>
To: okorpil@fh-landshut.de
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: [more info - please help!] MPC7455 DMA buffer strangeness
Date: Mon, 05 Jul 2004 18:15:49 +0200 [thread overview]
Message-ID: <40E97EB5.2040008@fh-landshut.de> (raw)
I checked my Page Table Entries (PTEs) for the MPC7455 and MPC8240 after the
remap_page_range() took place.
Except for the RPN part (the physical address of the page) the PTEs match,
ending with the last 11 Bits (flags as in arch/ppc/mm/pgtable.h):
Kernel space: 0x581
User space: 0x72D
(for user space this does mean - from least significant to most significant:
Page present: no,
Hashed PTE: yes,
User mode: yes,
Guarded: yes,
Coherent: no,
Inihibited: yes,
Write-Through: no,
Changed: no,
Referenced: yes,
Exec: yes,
Read-Write: yes.)
This does look correct for my application. But it does yield different results
on the two processors, while both seem to definitely match the same physical
address (the 1st 21 bits do match in the Linux PTEs).
How are these Linux PTEs mapped to the MMU PTEs (64 bit wide descriptors)?
The "Programming Environments Manual For 32-Bit Implementations of the PowerPC
Architecture", the MPC603e and MPC7450 reference manuals depict a completely
different format, so how and where are these converted? (Hopefully not in
assembler! ;) )
I'm so confused by this! It doesn't seem logical that I cannot access those
buffers correctly!
Thanks in advance,
Oliver Korpilla
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next reply other threads:[~2004-07-05 16:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 16:15 Oliver Korpilla [this message]
2004-07-05 23:44 ` [more info - please help!] MPC7455 DMA buffer strangeness Paul Mackerras
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=40E97EB5.2040008@fh-landshut.de \
--to=okorpil@fh-landshut.de \
--cc=linuxppc-embedded@lists.linuxppc.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 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.