From: Andreas Schwab <schwab@linux-m68k.org>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: Michael Schmitz <schmitzmic@gmail.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
linux-m68k@vger.kernel.org
Subject: Re: [PATCH RESEND 4/4] m68k/atari: fix SCC initialization for debug console
Date: Mon, 26 May 2014 19:44:24 +0200 [thread overview]
Message-ID: <87egzgh1tz.fsf@igel.home> (raw)
In-Reply-To: <alpine.LNX.2.00.1405262200390.10801@nippy.intranet> (Finn Thain's message of "Mon, 26 May 2014 22:03:07 +1000 (EST)")
Finn Thain <fthain@telegraphics.com.au> writes:
> I'll see what I can find also. Do you know of any hardware reference
> material available on the web?
If you can read German then the best reference is probably the Atari
Profibuch (http://atariprofibuch.de/).
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."
prev parent reply other threads:[~2014-05-26 17:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 5:27 [PATCH RESEND 0/4] m68k: earlyprintk and debug console improvements Finn Thain
2014-04-11 5:27 ` [PATCH RESEND 1/4 v2] m68k: toward platform agnostic framebuffer debug logging Finn Thain
2014-04-11 5:27 ` [PATCH RESEND 2/4 v2] m68k: multi-platform EARLY_PRINTK Finn Thain
2014-04-11 5:28 ` [PATCH RESEND 3/4] m68k/mvme16x: adopt common boot console Finn Thain
2014-04-11 9:19 ` Geert Uytterhoeven
2014-04-12 1:40 ` Finn Thain
2014-04-11 5:28 ` [PATCH RESEND 4/4] m68k/atari: fix SCC initialization for debug console Finn Thain
2014-05-25 9:09 ` Geert Uytterhoeven
2014-05-25 10:37 ` Finn Thain
2014-05-26 1:23 ` Michael Schmitz
2014-05-26 4:30 ` Finn Thain
2014-05-26 1:18 ` Michael Schmitz
2014-05-26 8:56 ` Michael Schmitz
2014-05-26 9:28 ` Geert Uytterhoeven
2014-05-26 11:43 ` Finn Thain
2014-05-26 12:03 ` Finn Thain
2014-05-26 17:44 ` Andreas Schwab [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=87egzgh1tz.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=fthain@telegraphics.com.au \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=schmitzmic@gmail.com \
/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