[hatari-devel] Falcon mode enabling DSP by default

[Laurent Sallafranque]

>  Btw. I noticed that DSP isn't reseted in Reset_ST() although e.g. Crossbar
>  and Videl are reseted there.  Should it be?

I think it should be reseted too.

About reset, when I reset any demo or game, there's always a looping 
sound that only stops if I do another reset.
Do you have the same behaviour ?

I haven't found why yet, as crossbar seems to be resetted.
It may comes from the dsp not reseted and still sending datas to the 
crossbar (VIA the SSI)

Regards,

Laurent


Le 15/01/2011 13:31, Eero Tamminen a écrit :
> Hi,
>
> On lauantai 15 tammikuu 2011, Nicolas Pomarède wrote:
>> BTW : when switching to tos 4, Hatari ask to reboot and go in Falcon
>> mode. I think we should enable DSP now by default when doing so,
> Good point, I commited that change.
>
> However I get different results with these:
> 	hatari --machine falcon --dsp emu --tos tos404.img mahabhar/
> 	hatari --tos tos404.img mahabhar/
>
> With latter the Mahabharata demo doesn't work.
>
> In the latter case these happen in main.c:
>          SDLGui_Init();
>          Printer_Init();
>          RS232_Init();
>          Midi_Init();
>          Screen_Init();
>          Main_SetTitle(NULL);
>          HostScreen_Init();
>          DSP_Init();
>          Floppy_Init();
>          M68000_Init();                /* Init CPU emulation */
>          Audio_Init();
>          DmaSnd_Init();
>          Keymap_Init();
>          /* Init HD emulation */
>          HDC_Init();
>          Ide_Init();
>          GemDOS_Init();
>
> before TOS4 setting forces these:
>                  ConfigureParams.System.nDSPType = DSP_TYPE_EMU;
>                  ConfigureParams.System.nMachineType = MACHINE_FALCON;
>                  ConfigureParams.System.nCpuFreq = 16;
>                  IoMem_Init();
>                  ConfigureParams.System.nCpuLevel = 3;
>                  M68000_CheckCpuLevel();
>
> Does the stuff done in main.c before this have anything that could depend
> from the above falcon setting?
>
>
>> it's not easily guessable for a normal user to know he must also choose to
>> enable DSP in the UI.  DSP should be stable enough to be enabled by
>> default ?
> Yes, enabling it doesn't anymore break programs like it did around
> Hatari v1.0. There's no known program that would work worse with
> DSP than without...  Unless you count the breaking sound (some progs
> have sound only with DSP) and Hatari being slower as "worse".
>
>
> Hm.  Actually that's not completely true.  If one uses EmuTOS in Falcon
> mode, some programs work without DSP, but not with DSP.  This is an issue
> because we ship EmuTOS with Hatari.
>
> So, enabling DSP for TOS4 is good, but doing it for e.g. "--machine falcon"
> isn't until EmuTOS is fixed and such version accompanies Hatari.
>
>
>> If user wants and know what it does, he can disable it later, but choosing
>> a "Falcon" should enable all possible component I think.
> Right, I don't think we should force it in the UI as the DSP option is
> in same dialog with machine selection.  Forcing it there would mean that
> user couldn't disable it.
>
>
> Btw. I noticed that DSP isn't reseted in Reset_ST() although e.g. Crossbar
> and Videl are reseted there.  Should it be?
>
> Currently it's reseted:
> - before memory snapshot is loaded
> - from psg.c
> - by TOS4 on startup I think (but not EmuTOS I guess)
>
>
> 	- Eero
> _______________________________________________
> hatari-devel mailing list
> hatari-devel at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/hatari-devel
>
>