linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Ingmar" <i2a@gmx.net>
To: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: exception vectors
Date: Mon, 31 Oct 2005 01:35:49 +0100	[thread overview]
Message-ID: <20051031002926.M71008@quicknet.nl> (raw)
In-Reply-To: <1130645036.29054.229.camel@gaston>

Hi all,

I am trying to overwrite the exception vector space of an ibook G4 :).

I have set up (for every exception) a small piece of code, that's a prefix of a
handler to be called. My problem is, that writing the “small” chunks of code to
the exception vector space gives no problem(so it seams) but writing all the
pieces of code as one chunk gives a exception [dsi, dsisr 0x42000000], this
indicates a store problem.

I have tried different modes of copying, mmu on/off, also chanced the WING bit,
switched the exception prefix on.

I don't believe putting the exception vectors to there “place” one by one is the
right way, in the Linux kernel the kernel get relocated and the code comes into
place. I have taken this as an example, unfortunately to to result :(..

 - Am I overlooking something?
 - Is the a “standard way” to overwrite the exception vector space of a powerpc?

ThankZ,
  Ingmar

  parent reply	other threads:[~2005-10-31  0:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-30  4:03 30 bits DMA and ppc Benjamin Herrenschmidt
2005-10-30  8:47 ` [Bcm43xx-dev] " Michael Buesch
2005-10-30 17:59 ` Olof Johansson
2005-10-30 21:14   ` Benjamin Herrenschmidt
2005-10-30 21:35     ` Olof Johansson
2005-10-30 21:41       ` Benjamin Herrenschmidt
2005-10-30 22:02         ` Olof Johansson
2005-10-31  0:35 ` Ingmar [this message]
2005-10-31  2:17   ` exception vectors Benjamin Herrenschmidt
2005-10-31  2:28   ` Hollis Blanchard
2005-10-31  9:58     ` Ingmar
2005-11-01  1:46       ` Olof Johansson
2005-11-01  8:28         ` Ingmar

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=20051031002926.M71008@quicknet.nl \
    --to=i2a@gmx.net \
    --cc=linuxppc-dev@ozlabs.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).