From: Kumar Gala <galak@kernel.crashing.org>
To: Wang Matthew-R59995 <Qi.W@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Linuxppc-embedded Digest, Vol 26, Issue 36
Date: Wed, 18 Oct 2006 20:54:24 -0500 [thread overview]
Message-ID: <39D16244-1677-4ED0-99CD-C1A1F393D140@kernel.crashing.org> (raw)
In-Reply-To: <54A124D27BDE0F449E2032F42ED617583197CD@zch01exm21.fsl.freescale.net>
On Oct 18, 2006, at 8:10 PM, Wang Matthew-R59995 wrote:
> Hi Kumar,
>
> Actually I do many trials about it. Vxwerks Bootrom is smaller than
> U-Boot. The key difference between Bootrom and U-boot is that some
> source code of Bootrom is invisible to the users.
>
> Actually the rfi instruction which I point out is the first rfi
> instruction of Linux PowerPC bringup.
>
> Before that, it's TLB entry invalidation and temp TLB entry mapping.
>
> I check MMU setting carefully before coming Linux Kernel.
>
> I just want to know if other guys met similar scenario like me. I
> don't
> need the precise answer, just overall suggestion about it because I
> understand that not everyone has the same bootloader of mine, that
> bootloader is actually a customized bootloader.
I understand that, thus I was asking what exact problem you were
seeing to try and help.
> Anyway thank you.
>
> R9 point to LR register, mask the high 20 bit of r9 and send to r7,
> and
> then add 24, which means stride 6 instructions for rfi instruction
> execution.
>
> Of course, rfi can switch the TLB entry, both the previous TLB
> entry and
> the temp TLB entry point to the same physical address.
>
> I've checked it.
I know what the code does, I wrote it :)
- kumar
prev parent reply other threads:[~2006-10-19 1:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.354.1161187327.32299.linuxppc-embedded@ozlabs.org>
2006-10-19 1:10 ` Linuxppc-embedded Digest, Vol 26, Issue 36 Wang Matthew-R59995
2006-10-19 1:54 ` Kumar Gala [this message]
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=39D16244-1677-4ED0-99CD-C1A1F393D140@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=Qi.W@freescale.com \
--cc=linuxppc-embedded@ozlabs.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.