All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Matthias Reis" <matthias.reis@physik.tu-berlin.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Matthias Reis <matthias.reis@physik.tu-berlin.de>,
	linux-m68k@vger.kernel.org
Subject: Re: Autovector exceptions on Atari ST
Date: Wed, 24 Aug 2011 21:47:37 +0200	[thread overview]
Message-ID: <7aefed5bdc7af1311db846ae00fb1359.squirrel@www.physik.tu-berlin.de> (raw)
In-Reply-To: <CAMuHMdXMd0iuE7FnhSRjFiO7A0TUVRfp-FdJ==RktU+9HspEJQ@mail.gmail.com>

> On Sun, Aug 7, 2011 at 23:09, Geert Uytterhoeven <geert@linux-m68k.org>
> wrote:
>
> MFP interrupts are not autovector interrupts, but user vector interrupts.
>
> Sorry, I forgot about this: it may be a stack frame format issue,
> which causes the kernel to
> incorrectly identify the interrupt number.
>
> user_inthandler() in arch/m68k/kernel/entry_mm.S looks at the
> PT_OFF_FORMATVEC
> field in the stack frame to identify the interrupt source. I don't
> know from memory
> if the plain 68000 stores it there. For autovector interrupts, it
> doesn't, that's why
> I created inidividual auto*_inthandler() functions that put an hardcoded
> number
> on the stack instead of looking at the stack frame.
>

Hi Geert,

thanks for your kind reply. As far as I understand the 68000 manual
(http://www.freescale.com/files/archives/doc/ref_manual/M68000PRM.pdf,
section b.2), the CPU does not store the vector number on the exception
stack. This is also what I've seen in the debugger: some seemingly bogus
irq number is passed to m68k_handle_int. Any suggestions how to solve
this? I guess it is not a good idea to write an individual
user*_inthandler for each of the 255-64=191 possible user interrupts.

Best regards,
Matthias

  reply	other threads:[~2011-08-24 19:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02 19:25 Support for MMU-less Atari ST Matthias Reis
2011-06-03  7:04 ` Greg Ungerer
2011-06-03  7:43   ` Geert Uytterhoeven
2011-06-04  9:14     ` Geert Uytterhoeven
2011-06-04 12:23       ` Matthias Reis
2011-08-07 20:57         ` Autovector exceptions on " Matthias Reis
2011-08-07 21:09           ` Geert Uytterhoeven
2011-08-23 18:22             ` Geert Uytterhoeven
2011-08-24 19:47               ` Matthias Reis [this message]
2011-08-25  1:51                 ` Joshua Juran
2011-08-25  8:13                   ` Geert Uytterhoeven
2011-08-25 11:38                     ` Greg Ungerer
2011-06-03 10:54   ` Support for MMU-less " Finn Thain

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=7aefed5bdc7af1311db846ae00fb1359.squirrel@www.physik.tu-berlin.de \
    --to=matthias.reis@physik.tu-berlin.de \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@vger.kernel.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.