public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] mpc85xx debug TLB entry
Date: Wed, 10 Oct 2012 19:21:30 -0500	[thread overview]
Message-ID: <1349914890.21493.14@snotra> (raw)

I'm debugging some SPL changes and am still having a hard time  
following the initial TLB flow.  We seem to be creating an entry in AS0  
-- how is that not conflicting with the TLB entry we're running from?   
Why is the debug TLB 256K?  Why is it not aligned to 256K?  How do you  
know that MAS2_I is correct (it should be cacheable in the  
loaded-by-spl case)?

I'm trying to get the p2020rdb-pca SPL payload to run out of L2 SRAM,  
and I see weird TLB behavior causing a hang if I don't comment out the  
debug TLB.

-Scott

             reply	other threads:[~2012-10-11  0:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-11  0:21 Scott Wood [this message]
2012-10-11  9:01 ` [U-Boot] mpc85xx debug TLB entry Prabhakar Kushwaha
2012-10-11 15:21   ` Scott Wood
2012-10-13  0:43     ` Scott Wood
2012-10-11  9:13 ` Prabhakar Kushwaha

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=1349914890.21493.14@snotra \
    --to=scottwood@freescale.com \
    --cc=u-boot@lists.denx.de \
    /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