From: Michael Uhler <uhler@mips.com>
To: Kang <huangyk@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Problem caused by forcing interrupt vector location to 0x91xx0200 instead of 0x80000200
Date: 14 Oct 2004 18:39:32 -0700 [thread overview]
Message-ID: <1097804372.6997.81.camel@uhler-linux.mips.com> (raw)
In-Reply-To: <8498a8b0041014182933ca742a@mail.gmail.com>
Prior to Release 2 of the MIPS32 Architecture, the exception vectors
were fixed at a base of 0x80000000, which put the vectored interrupt
offset at 0x80000200.
The MIPS32 4Kc processor is an implementation of Release 1 of the
Architecture, so it has a fixed exception vector base. (Note that
the MIPS32 4KEc - the added 'E' is significant - implements Release 2
so in case you mis-typed, there is a solution using the 4KEc).
So with a Release 1 implementation, your only really solution is
to put a jump at 0x80000200 to where you want the code to be.
I suspect that this isn't really what you want.
/gmu
On Thu, 2004-10-14 at 18:29, Kang wrote:
> Hello buddies,
>
> I am working on a MIPS4Kc based reference design board. For some
> reason, I need to force the interrupt vector location to address
> 0x91xx0200 instead of 0x80000200 in arch/mips/kernel/traps.c. The
> kernel was loaded into 0x91xxxxxx space as well.
>
> The kernel hung just after the interrupt was first time opened, after
> sti(), before calibrate_delay() in init/main.c. It was weird that I
> didn't see any problem if I put interrupt vector to location
> 0x80000200 while all other exception vectors to 0x91xxxxxx.
>
> Was interrupt vector location hardcode to the address 0x80000200? Or
> some other place I need to change to walk around it. Any idea?
>
> Thanks a bunch for your help.
>
> Leo
--
Michael Uhler, Chief Technology Officer
MIPS Technologies, Inc. Email: uhler@mips.com
1225 Charleston Road
Mountain View, CA 94043
prev parent reply other threads:[~2004-10-15 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-15 1:29 Problem caused by forcing interrupt vector location to 0x91xx0200 instead of 0x80000200 Kang
2004-10-15 1:39 ` Michael Uhler [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=1097804372.6997.81.camel@uhler-linux.mips.com \
--to=uhler@mips.com \
--cc=huangyk@gmail.com \
--cc=linux-mips@linux-mips.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.