linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Frank Rowand <frank_rowand@mvista.com>
To: Hua Ji <hji@netscreen.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: About TLB mapping
Date: Thu, 25 Jan 2001 19:10:47 -0800	[thread overview]
Message-ID: <3A70EAB7.C46E3CD3@mvista.com> (raw)
In-Reply-To: A33AEFDC2EC0D411851900D0B73EBEF7063E87@NAPA


Hua Ji wrote:
>
> Hi, folks,
>
> Advice needed.
>
> I am writting my TLB mapping for 405GP 128M physical memory.
> When I try to assemble my codes. I got some error called:
> "Unrecognized opcode: tlbwe".

Why are you doing this?  Is something wrong with the existing
implementation?


> I am confused and am asking for help. Thanks in advance.
>
> Or do I missed some options for my make file? My working environment is:
> *  powerpc-eabi-gcc and corresponding as....
> *  I tried to use -mcpu=405 to let as know that I am expecting 405cpu:-)

I don't know of any compiler that has -mcpu=405 (yet).  Use -mcpu=403.


> #-------------
> #Error Message I got from compiler and assember
> #------------------------------------------
>  : Error: Unrecognized opcode: `tlbwe'
>  : Error: Unrecognized opcode: `tlbwe'
>
> #-------------
> #My codes sample
> #-----------------------------------------------------
>  li      %r0,0                 #TLB Entry 0
>  tlbwe  %r4,%r0,1
>  tlbwe  %r3,%r0,0
> #-----------------------------------------------------

Thanks,

Frank
--
Frank Rowand <frank_rowand@mvista.com>
MontaVista Software, Inc

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

      reply	other threads:[~2001-01-26  3:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-26  0:42 About TLB mapping Hua Ji
2001-01-26  3:10 ` Frank Rowand [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=3A70EAB7.C46E3CD3@mvista.com \
    --to=frank_rowand@mvista.com \
    --cc=frowand@mvista.com \
    --cc=hji@netscreen.com \
    --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).