Re: [hatari-devel] SCC issues (vs. real MegaSTE) mentioned in Atari-forum

[Thomas Huth <th.huth@xxxxxxxxx>]

On 10/09/2024 16.38, Nicolas Pomarède wrote:
> Le 08/09/2024 à 13:06, Eero Tamminen a écrit :
> > Hi,
> >
> > On 7.9.2024 16.34, Nicolas Pomarède wrote:
> > > Le 04/09/2024 à 23:48, Eero Tamminen a écrit :
> > > > There are couple of SCC issues mentioned on Atari forum compared to how 
> > > > things work on real MegaSTE:
> > > > https://www.atari-forum.com/viewtopic.php?p=459561#p459561
> > >
> > > just to be sure, from what the user is telling, doesn't he refer to 
> > > serial port through MFP and not through SCC ?
> > >
> > > He made some tests in february, but at that time Hatari 2.5 was not 
> > > released yet, so it was using the old SCC code.
> > >
> > > and it's not clear when he says he tried git version, what port did he try ?
> >
> > I asked about that, but it may be better for you to ask more detailed 
> > questions there, as I'm not really familiar with MFP/SCC or SW using those...
>
> Hi
>
> from his answer I see some code is not present in MFP case as in SCC to 
> handle DCD signal.
>
> I'm looking at this to make both code more similar but I see rs232.c is 
> using File_Open to open the in/out file associated with the serial port, and 
> not using open() directly as in scc.c
>
> Is there any reason for that ? I see File_Open allows to use stderr and 
> stdout as a filename but is that really used for rs232 emulation ?

At least on Linux, one could also use open() with /dev/stderr or /dev/stdout 
for that.

> If not, I'd rather replace use of "FILE *" handler by file descriptor number 
> (as returned by open() )
>
> Any idea on that ?

I think it's mainly that way since this is based on very old WinSTon code. 
Back then, I rather replaced the Windows functions with the portable fopen() 
etc. instead of using the low-level functions instead.

 Thomas