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

[Eero Tamminen <oak@xxxxxxxxxxxxxx>]

Hi,

On 11.9.2024 10.06, Nicolas Pomarède wrote:
> Le 10/09/2024 à 23:39, Eero Tamminen a écrit :
> > Hatari "--help" states:
> > <file>    Devices accept also special 'stdout' and 'stderr' file names
> >
> > I.e. it's a documented Hatari feature that's supposed to work for all 
> > devices.
> >
> > And one of the reasons why all Hatari debug/trace/log output goes 
> > (should go) by default to stderr nowadays, instead of some of it going 
> > to stdout.
> >
> > That way one can eg. pipe Atari device output directly from Hatari to 
> > another command (when using "stdeout"), or mix it with Hatari 
> > debug/trace output (when using "stderr").
> >
> > How useful that is, depends on the device.
>
> ok for piping, but as you say is that really useful / used, as this only 
> exist for rs232/mfp and not scc ?

File_Open() is used by MIDI, printer and RS232 emulation i.e. SCC is 
only one lacking it.


> > Why you want to use FD?
>
> I know I can get fd from file*, that would just remove an extra layer of 
> file abstraction and deal directly with more "low level" calls like 
> "open()".
>
> Looking at the code we can see that on nearly every rs232 functions 
> file* is converted to fd to do the real job (especially for ioctl) that 
> why I wondered why it was this way.
>
> Using FD would allow to have similar logic/code between serial in mfp 
> and scc, making it easier to fix mfp to better handle DCD and other 
> signals.

It's up to you, but if you change it, update also Opt_ShowHelp() output.


	- Eero