All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kang <huangyk@gmail.com>
To: linux-mips@linux-mips.org
Subject: Problem caused by forcing interrupt vector location to 0x91xx0200 instead of 0x80000200
Date: Thu, 14 Oct 2004 21:29:23 -0400	[thread overview]
Message-ID: <8498a8b0041014182933ca742a@mail.gmail.com> (raw)

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

             reply	other threads:[~2004-10-15  1:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-15  1:29 Kang [this message]
2004-10-15  1:39 ` Problem caused by forcing interrupt vector location to 0x91xx0200 instead of 0x80000200 Michael Uhler

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=8498a8b0041014182933ca742a@mail.gmail.com \
    --to=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.