From: Petr Stehlik <pstehlik@sophics.cz>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Linux/m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: [PATCH] m68k: Revive reporting of spurious interrupts
Date: Thu, 14 Jul 2011 08:32:54 +0200 [thread overview]
Message-ID: <1310625174.18428.2.camel@joy-desktop> (raw)
In-Reply-To: <alpine.DEB.2.00.1107132028080.31317@ayla.of.borg>
Geert Uytterhoeven píše v Wed 13. 07. 2011 v 20:29 +0200:
> commit 2502b667ea835ee16685c74b2a0d89ba8afe117a ("Change the m68knommu irq
> handling to use the generic irq framework.") removed the reporting of spurious
> interrupts on nommu (68328 and 68360).
>
> Bring it back in a generic way, using "atomic_t irq_err_count", as that's what
> most of the other architectures are using.
I am curious if this would fix the kernel running in FastRAM on Falcon
with Afterburner040 (MC68040) by any chance. Because that never worked
correctly and there always were a lot of spurious interrupts :-)
If/when there is a binary kernel 3.1 for Falcon040 I might give it a
try, just out of curiosity.
Petr
next prev parent reply other threads:[~2011-07-14 6:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 18:29 [PATCH] m68k: Revive reporting of spurious interrupts Geert Uytterhoeven
2011-07-14 3:47 ` Greg Ungerer
2011-07-14 6:32 ` Petr Stehlik [this message]
2011-07-14 7:20 ` Geert Uytterhoeven
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=1310625174.18428.2.camel@joy-desktop \
--to=pstehlik@sophics.cz \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.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