From: Ralph Siemsen <rsiemsen@rossvideo•com>
To: linuxppc-dev@lists•linuxppc.org
Subject: Re: early UART mapping in head_44x.S
Date: Tue, 13 Jul 2004 17:51:47 -0400 [thread overview]
Message-ID: <40F45973.7080908@rossvideo.com> (raw)
In-Reply-To: <40F452D6.9020806@rossvideo.com>
Ralph Siemsen wrote:
> Can anyone explain how this is meant to work? Specifically, the
> ori r3,r3,PPC44x_TLB_TS
> would clear the other bits in this register, including the "valid" bit,
> so how is this mapping supposed to work?
Clearly demonstrating that I have been staring that this line of code
too long... the ori instruction sets the TS bit and shouldn't affect the
others...
However, if I dump the TLB entry after the isync using the BDI
interface, it shows the EPN is zero'd out:
IDX TID EPN SIZE VTS RPN USER WIMGE USRSVC
1 : 00 00000000 1KB -0 -> 1_40000000 U:0000 -I-G- -WR-WR
whereas without the second "tlbwe" instructions, I get the expected and
functioning mapping:
1 : 00 e0000000 256MB V0 -> 1_40000000 U:0000 -I-G- ----WR
What's the secret?
-R
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
** This list is shutting down 7/24/2004.
next prev parent reply other threads:[~2004-07-13 21:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 21:23 early UART mapping in head_44x.S Ralph Siemsen
2004-07-13 21:51 ` Ralph Siemsen [this message]
2004-07-13 22:28 ` James Perkins
2004-07-13 22:48 ` Ralph Siemsen
2004-07-22 23:55 ` Matt Porter
-- strict thread matches above, loose matches on Subject: below --
2004-08-02 12:30 Daren Hayward
2004-08-02 13:57 ` Matt Porter
2004-08-03 17:58 ` Ralph Siemsen
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=40F45973.7080908@rossvideo.com \
--to=rsiemsen@rossvideo$(echo .)com \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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