From: Andreas Schwab <schwab@linux-m68k.org>
To: Alan Hourihane <alanh@fairlite.co.uk>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Finn Thain <fthain@telegraphics.com.au>,
Thorsten Glaser <tg@mirbsd.de>,
debian-68k@lists.debian.org,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: Atari TT
Date: Fri, 06 Jan 2012 00:35:35 +0100 [thread overview]
Message-ID: <m2wr95n2ns.fsf@linux-m68k.org> (raw)
In-Reply-To: <4F05FCC3.7060306@fairlite.co.uk> (Alan Hourihane's message of "Thu, 05 Jan 2012 19:40:51 +0000")
Alan Hourihane <alanh@fairlite.co.uk> writes:
> Could these spurious interrupts be generated by the debug path, because
> I'm now using it to output debug data ?
None of the debug devices are touching tt_mfp (ser2 uses the SCC, and
ser1 uses st_mfp).
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2012-01-05 23:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F0488A9.5030100@fairlite.co.uk>
[not found] ` <Pine.BSM.4.64L.1201041911580.19192@herc.mirbsd.org>
[not found] ` <alpine.LNX.2.00.1201052128060.6601@nippy.intranet>
[not found] ` <4F059460.5040305@fairlite.co.uk>
[not found] ` <CAMuHMdUxQq_29g7yeaS2Ktz193CcHNX5FaP8PR9ijU0htnKbZg@mail.gmail.com>
[not found] ` <4F059AE1.6070707@fairlite.co.uk>
[not found] ` <4F059DB9.1050209@fairlite.co.uk>
2012-01-05 14:42 ` Atari TT Geert Uytterhoeven
2012-01-05 15:49 ` Andreas Schwab
2012-01-05 19:40 ` Alan Hourihane
2012-01-05 23:35 ` Andreas Schwab [this message]
2012-01-05 17:04 ` Alan Hourihane
2012-01-05 19:02 ` Alan Hourihane
2012-01-05 20:35 ` Geert Uytterhoeven
2013-01-20 16:52 ` Thorsten Glaser
[not found] <20130120205231.GC32291@mail.biophys.uni-duesseldorf.de>
[not found] ` <Pine.BSM.4.64L.1301202117270.27441@herc.mirbsd.org>
[not found] ` <20130120225718.GA1459@mail.biophys.uni-duesseldorf.de>
[not found] ` <Pine.BSM.4.64L.1301232011550.14843@herc.mirbsd.org>
[not found] ` <20130123212251.GA14282@mail.biophys.uni-duesseldorf.de>
[not found] ` <Pine.BSM.4.64L.1301232213380.14843@herc.mirbsd.org>
[not found] ` <20130124000856.GA15759@mail.biophys.uni-duesseldorf.de>
[not found] ` <Pine.BSM.4.64L.1301241759530.6423@herc.mirbsd.org>
[not found] ` <20130124185341.GA27701@mail.biophys.uni-duesseldorf.de>
[not found] ` <Pine.BSM.4.64L.1301241946080.6423@herc.mirbsd.org>
2013-01-24 20:20 ` Michael Schmitz
2013-01-24 20:41 ` Geert Uytterhoeven
2013-01-24 21:48 ` Michael Schmitz
2013-01-25 7:30 ` Geert Uytterhoeven
2013-01-25 8:14 ` Michael Schmitz
2013-01-24 20:50 ` Thorsten Glaser
2013-01-25 7:33 ` 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=m2wr95n2ns.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=alanh@fairlite.co.uk \
--cc=debian-68k@lists.debian.org \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=tg@mirbsd.de \
/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.