From: Dan Malek <dan@embeddededge.com>
To: "Matthew S. McClintock" <mattsm@arlut.utexas.edu>
Cc: fabidi@ultsol.com, linuxppc-embedded@lists.linuxppc.org
Subject: Re: TLB and CSSBAR problems with MPC8540 and BDI2000
Date: Tue, 13 Jan 2004 20:43:06 -0500 [thread overview]
Message-ID: <40049EAA.6030709@embeddededge.com> (raw)
In-Reply-To: 1073938758.5575.140.camel@chuck.arlut.utexas.edu
Matthew S. McClintock wrote:
> So that leaves us back at the original question. Why does configuring
> the cpu via bdi2000 prevent me from using my u-boot image? Any other
> ideas?
Yep. I have one now. Make sure your u-boot image also has a TLB1
entry for your "default" CCSRBAR. Further, make sure your BDI init
section doesn't move the CCSRBAR from the default value assumed by
your u-boot image. I had the latter correct, just didn't realize
that a "TLB1 flash invalidate" command to the MMUCSR0 doesn't seem
to honor the 'invalidate protect' in the TLB entry. Everything
works fine when you get all of the ducks in a row :-)
Of course, we should be discussing this on the u-boot list,
not on this one........
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-14 1:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-09 5:41 [Q] question about using x86 gdb to debug the remote ppc target (kgdb) kotaeji
2004-01-09 5:50 ` John Zhou
2004-01-09 16:42 ` Christopher R. Johnson
2004-01-09 17:40 ` TLB and CSSBAR problems with MPC8540 and BDI2000 Fahd Abidi
2004-01-09 17:54 ` Dan Malek
2004-01-09 19:45 ` Matthew S. McClintock
2004-01-09 22:13 ` Dan Malek
2004-01-09 22:18 ` Matthew S. McClintock
2004-01-09 22:28 ` Dan Malek
2004-01-12 15:56 ` Dan Malek
2004-01-12 20:19 ` Matthew S. McClintock
2004-01-14 1:43 ` Dan Malek [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-14 17:19 Milliorn Gary-rxcr80
2004-01-14 18:39 ` Dan Malek
2004-01-28 15:57 ` Matthew S. McClintock
2004-01-28 16:10 ` Kumar Gala
2004-01-28 16:47 ` Matthew S. McClintock
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=40049EAA.6030709@embeddededge.com \
--to=dan@embeddededge.com \
--cc=fabidi@ultsol.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=mattsm@arlut.utexas.edu \
/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).