| Re: [hatari-devel] SCC-B support |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] SCC-B support
- From: Thomas Huth <th.huth@xxxxxxxxx>
- Date: Tue, 1 Jan 2019 15:30:38 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1546353041; bh=xStMdPHI9MbDovBpNV/1NyPq8FLinf8GG6GV8slh7ik=; h=Date:From:To:Subject:From; b=ozgfWwxNd8935ROgRGhiOG2Y6o943Cn/3t7uLWkxA6qAiOMDXNPGMPvDs3KT49qaA XIbJurwgEfMOLnRVpw+xZ4ZuB/HYqmkXfV6TKGsdHXumsYJ7GgFrDuG+cWtCbRRFmc 27/ulB5G10Aom3517DNVBg7R+iV8DO9KAcCYKDtd/u/sFMnrQLO7u0j8lZhgvjuN8N LvQ+Jt/kj71TXNNOobLMc7vtS2nqVc97X/QUhpXh6Mp+e5FsqEkYiWPRcnlcDE1l28 i3eHjEOQANjGP15Phh71VbCOHuEctHksBhJQYMcmqWShyXH7wXnDr2/4VY33tlpOtR rHYC91cuJ1ZCA==
Am Tue, 1 Jan 2019 13:19:40 +0200
schrieb Eero Tamminen <oak@xxxxxxxxxxxxxx>:
> Hi,
>
> Le 30/12/2018 à 20:07, Christian Zietz a écrit :
> > Eero Tamminen schrieb:
> >> If I've understood correctly:
> >> * ST / MegaST / STE: 1 MFP serial port
> >> * MegaSTE & TT: 1 MFP, 2x SCC serial ports
> >
> > Actually: Real TT: 2 MFP, 2 SCC serial ports, although one of the
> > SCC ports is shared with the so-called "LAN" port of the TT.
> > However, the second MFP of the TT isn't emulated by Hatari.
>
>
> On 1/1/19 10:40 AM, Thomas Huth wrote:> Am Sun, 30 Dec 2018 20:43:10
> +0200
> > schrieb Eero Tamminen <oak@xxxxxxxxxxxxxx>:
> >> * Falcon: 2 SCC serial ports >
> > As far as I know, the Falcon has only one serial port. SCC-A is
> > hard-wired to the "LAN" connector here (while it can be switched to
> > a normal serial connector for the TT and Mega-STE). The code that
> > I've copied from Aranym does not fully support the SCC-A channel
> > yet, so not sure whether it makes sense to provide a "--scc-a"
> > parameter already... Let's focus on SCC-B for now which is way more
> > important, since it is the only serial port of the Falcon.
>
> In that case it could be more user-friendly if the file options
> would talk about ports instead of Atari internal chips.
>
> I.e. with these:
>
> --rs232-in <file> Enable serial port, use <file> as input device
> --rs232-out <file> Enable serial port, use <file> as output device
>
> being wired on Falcon to SCC-B, and to MFP-1 everywhere else.
So when you have a program that uses the SCC, you have to adjust the
options depending on the machine type that you are using? ... I don't
think that I'll like that idea.
> With MegaSTE/TT eventually supporting additionally:
>
> --rs232-2-in
> --rs232-2-out
> --rs232-3-in
> --rs232-3-out
> --rs232-4-in
> --rs232-5-out
>
> And those being mapped to MFP-2, SCC-A, SCC-B as explained
> in the documentation.
>
> Opinions?
Sounds also rather confusing to me, and this will make the code a lot
uglier, so I'd rather not do this.
Thomas