From: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
To: Jim Chapman <jim.chapman@iname.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Q: Register usage in mpc860 ports
Date: Fri, 21 May 1999 18:36:16 +0200 [thread overview]
Message-ID: <4.2.0.37.19990521183415.04a02b30@mail.lauterbach.com> (raw)
In-Reply-To: <37457D27.DA34E026@iname.com>
At 17:35 21.05.99 , Jim Chapman wrote:
>I am porting LinuxPPC to a custom embedded mpc860 board. I am starting
>with the mbx port and using home-built egcs-1.1.2 tools on a Linux
>host, using the instructions in
>http://members.home.com/mmporter/cross.html
>
>There seem to be register usage conflicts in the MMU TLB handlers. The
>code tries to use location 0 (according to the comment) to store a
>couple of register values, e.g. in arch/ppc/kernel/head.S
>
>InstructionTLBMiss:
> mtspr M_TW, r20 /* Save a couple of working registers */
> mfcr r20
> stw r20, 0(r0)
> stw r21, 4(r0)
>
>However, I am finding that r0 isn't zero when the MMU exceptions are
>taken. Instead, it points to somewhere in the text or data segment. I
>hacked the code to save r20 & r21 to a specific memory location and that
>fixed that particular problem.
r0 represents 0 in a number of PPC instructions, lookup stw in your PPC
assembler book.
Franz.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
prev parent reply other threads:[~1999-05-21 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-21 15:35 Q: Register usage in mpc860 ports Jim Chapman
1999-05-21 16:36 ` Franz Sirl [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=4.2.0.37.19990521183415.04a02b30@mail.lauterbach.com \
--to=franz.sirl-kernel@lauterbach.com \
--cc=jim.chapman@iname.com \
--cc=linuxppc-dev@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 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.