linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Brian Kuschak <bkuschak@yahoo.com>
To: bsimon@ctam.com.au
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: linuxppc embedded boot problems.
Date: Wed, 15 Dec 1999 20:08:25 -0800 (PST)	[thread overview]
Message-ID: <19991216040825.21140.qmail@web306.mail.yahoo.com> (raw)


> This code has statements to invalidate the cache
> before jumping to the
> kernel. Is this the same as making sure lines are
> not "locked" in the
> cache ?

No, lines which have been locked into cache can only
be removed by sending an "unlock line" or "unlock all"
command to the IC_CSR register.  "Invalidate all" does
not remove "locked" lines. 


> I have boot code which does basic initialisation of
> the 860
> (chipselects, DRAM, etc).  This code will eventually
> jump to the start
> of the "kernel loader".  Do I also have to
> invalidate the caches just
> before jumping to the kernel loader ?  This
> currently isn't done.  BTW.
> All caches are disabled at this stage so I guess it
> shouldn't matter.
> 

If caches are disabled, it's a non-issue.  We wrote
our own boot monitor for a custom 823 board
(originally running non-linux code), copying code from
a slow flash into fast SDRAM and swapping chip
selects.  If you are running in a region of memory
with I-Cache enabled, and you copy new code into that
memory, then invalidating the I-cache is necessary.

Brian

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~1999-12-16  4:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-16  4:08 Brian Kuschak [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-12-15  5:55 linuxppc embedded boot problems Brian Kuschak
1999-12-15 19:06 ` Dan Malek
1999-12-15 22:56   ` Brendan Simon
1999-12-16  5:03     ` Dan Malek
1999-12-14 22:12 Brendan Simon
1999-12-15  2:58 ` Dan Malek
1999-12-15  3:04   ` Brendan Simon
1999-12-15  4:11     ` Dan Malek
1999-12-15  3:51       ` Brendan Simon
1999-12-15 19:04         ` Dan Malek

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=19991216040825.21140.qmail@web306.mail.yahoo.com \
    --to=bkuschak@yahoo.com \
    --cc=bsimon@ctam.com.au \
    --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 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).