public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@gmail.com>
To: Eero Tamminen <oak@helsinkinet.fi>,
	linux-m68k <linux-m68k@lists.linux-m68k.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: Regression: Atari SCU support
Date: Thu, 20 Jun 2024 13:24:48 +1200	[thread overview]
Message-ID: <5ee6ef02-75ff-4d3b-b4c7-37da47a40a76@gmail.com> (raw)
In-Reply-To: <9aa793d7-82ed-4fbd-bce5-60810d8a9119@helsinkinet.fi>

Hi Eero,

while the workaround will shut up the unexpected interrupt messages, it 
still does not prevent that interrupt from happening.

falcon_hblhandler() will not set the IPL sufficiently high for that, and 
I do not know whether permanently setting IPL 4 will quiesce other 
system interrupts.

Setting tt_scu.sys_mask zero is indeed the preferred option.

If you or Christian want to submit a patch to that effect, I'll gladly 
add my review tag.

Cheers,

     Michael


On 20/06/24 02:43, Eero Tamminen wrote:
> Hi,
>
> During the development of Atari TT / MegaSTe SCU support for Hatari 
> emulator, it was noticed that m68k Linux does not properly initialize 
> SCU registers / IRQ handlers on boot.
>
> Currently Linux freezes at boot and spews "unexpected interrupt" 
> messages constantly on TT.
>
> Nicolas Pomarède and Christian Zietz investigated:
> * Issue to be due to VBL IRQ handler removal [1]
> * boot to succeed if either 0x00 is written to the SCU sys_mask 
> (preferred), or handler is provided for VEC_INT4 [2] when SCU is used
>
> Christian has verified the issue and its workaround on real Atari TT.
>
>
>     - Eero
>
> [1] 
> https://github.com/torvalds/linux/commit/1fa0b29f3a43f9dd8080d24cd16790b15ef963f5
> [2] 
> https://git.tuxfamily.org/hatari/hatari.git/tree/tools/linux/0004-WA-avoid-unexpected-SCU-interrupts.patch

      reply	other threads:[~2024-06-20  1:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-19 14:43 Regression: Atari SCU support Eero Tamminen
2024-06-20  1:24 ` Michael Schmitz [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=5ee6ef02-75ff-4d3b-b4c7-37da47a40a76@gmail.com \
    --to=schmitzmic@gmail.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=oak@helsinkinet.fi \
    /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