From: Alan Hourihane <alanh@fairlite.co.uk>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Thorsten Glaser <tg@mirbsd.de>,
Finn Thain <fthain@telegraphics.com.au>,
Michael Schmitz <schmitzmic@googlemail.com>,
linux-m68k@vger.kernel.org, debian-68k@lists.debian.org
Subject: Re: [RFC] m68k: Update defconfigs
Date: Thu, 05 Jan 2012 09:58:49 +0000 [thread overview]
Message-ID: <4F057459.3060101@fairlite.co.uk> (raw)
In-Reply-To: <CAMuHMdVN470=RBQMHZ9PQ_rNCVbS4gD0+5P654YdxrBR3aqotA@mail.gmail.com>
On 01/05/12 09:52, Geert Uytterhoeven wrote:
> On Wed, Jan 4, 2012 at 23:22, Thorsten Glaser <tg@mirbsd.de> wrote:
>> Geert Uytterhoeven dixit:
>>
>>> CONFIG_SERIAL_CONSOLE : y . . . . . . . . . . y
>> This is something I'd like to see, if it is possible from
>> the hardware: ARAnym’s emulated parallel port for debugging
>> is unidirectional (printing only), so, in headless mode,
>> you get no console at all (for logging in to fix the network,
>> see that it hangs in fsck, etc).
> I think ARAnyM's emulated serial port can do this, but we no longer have
> an Atari SCC driver.
>
> Finn, Michael: as pmaczilog uses platform devices, it can be made to work
> on Atari, too?
>
>> Do the other devices not have a serial port?
> We lost all serial drivers during the last few years, except for
> amiserial (which
> we may loose in the future, too, as it does things the serial core people
> don't like / consider unsafe).
>
Yikes,
When trying to bring up the TT and getting vertical lines (which appears
to be known about given the info on the wiki with lots of TTRAM ?), I
tried to use serial console only to find that atari_scc.c is no more. :-(
It would certainly be wonderful to have atari_scc.c back.
Any other alternatives for console debugging on physical Atari ?
Alan.
--
To UNSUBSCRIBE, email to debian-68k-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/4F057459.3060101@fairlite.co.uk
next prev parent reply other threads:[~2012-01-05 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 22:05 [RFC] m68k: Update defconfigs Geert Uytterhoeven
2012-01-04 22:22 ` Thorsten Glaser
2012-01-05 9:52 ` Geert Uytterhoeven
2012-01-05 9:58 ` Alan Hourihane [this message]
2012-01-05 10:03 ` Geert Uytterhoeven
2012-01-05 11:11 ` Finn Thain
2012-01-05 10:11 ` Petr Stehlik
2012-01-05 11:42 ` 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=4F057459.3060101@fairlite.co.uk \
--to=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=schmitzmic@googlemail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox