Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@oss.sgi.com>
To: Mike Manchip <michael.manchip@s3group.com>
Cc: linux-mips <linux-mips@oss.sgi.com>
Subject: Re: having trouble installing exceptions
Date: Fri, 28 Sep 2001 16:48:05 +0200	[thread overview]
Message-ID: <20010928164805.A31094@dea.linux-mips.net> (raw)
In-Reply-To: <016601c1481c$be873260$845978c1@temple.leop.s3group.com>; from michael.manchip@s3group.com on Fri, Sep 28, 2001 at 01:54:43PM +0100

On Fri, Sep 28, 2001 at 01:54:43PM +0100, Mike Manchip wrote:

> I'm currently trying to get the mips port to work on a galileo gt64115 board
> with a rm5231 chip.
> 
> I'm OK right until the point when I'm installing exceptions into
> non-cacheable space in arch/mips/kernel/traps.c
> 
> as soon as I memcpy except_vec3_generic to KSEG0 + 0x180 and flush the
> instruction cache, my machine hangs, and I can't see why!

KSEG0 is normally cached space.  If of some reason it's configured as
non-cachable and you're flushing caches funny things will happen.

> /* Copy the generic exception handler code to it's final destination. */
>  memcpy((void *)(KSEG0 + 0x80), &except_vec1_generic, 0x80);
>  memcpy((void *)(KSEG0 + 0x100), &except_vec2_generic, 0x80);
>  memcpy((void *)(KSEG0 + 0x180), &except_vec3_generic, 0x80);
>  flush_icache_range(KSEG0 + 0x80, KSEG0 + 0x200);
> 
> Is it possibly something to do with the monitor I'm using? I'm using both
> PROM and in desperation, a vxworks one (it can see the ethernet card, thus
> speeding up kernel loads tremendously).
> How does the monitor do exceptions? Do I have to do something special with
> exceptions when a monitor is present?

So firmware is operating with BEV set, thus won't use the vectors at
KSEG0 at all.

  Ralf

  reply	other threads:[~2001-09-28 14:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-28 12:54 having trouble installing exceptions Mike Manchip
2001-09-28 14:48 ` Ralf Baechle [this message]
2001-09-28 17:51 ` Jun Sun

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=20010928164805.A31094@dea.linux-mips.net \
    --to=ralf@oss.sgi.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=michael.manchip@s3group.com \
    /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