Re: [hatari-devel] hatari tt scc emulation |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] hatari tt scc emulation
- From: Uwe Seimet <Uwe.Seimet@xxxxxxxxx>
- Date: Mon, 17 Jul 2017 08:33:15 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1500273196; l=1287; s=domk; d=seimet.de; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Subject:To:From:Date; bh=LLrBvPOCLF9zJeSO9YqGf+ZalmNqOpsNn8k/vbP1F2g=; b=SJv8jcfMuXKwWF8UYDevmIbWnZ2VAk27XhlqdIL2kmOHAL3jscPboklXU6znRxwef0 MM6iReZiM4xLa1n+TB8DLt3UbkelYcXPFG0n5z69lstLCxdPwu+euXBDTWcQB0tZSyjR 1twVH7zJ+f6jwtv5NYPyg1S6hDyBf3AkNuu/o=
Hi,
> But i would ask, if it is a good solutio to generate a bus error for
> addresses used in a TT. If no bus erro was generated if MiNT tries
> to initialize the scc, nothing bad would happend because i did not
> use any software for serial communication. And MiNT would run on
> hatari TT emulation. Maybe it is worth to think about not generate
> a bus error but only do nothing if software tries to access hardware
> not yet emulated?
I general doing nothing is not such a good idea. There is software (several
hard disk drivers, but probably also other software) that detects whether a
particular hardware (ACSI, SCSI, IDE) is present by accessing the
corresponding hardware registers. If there is a bus error this signals
that the hardware that was checked for is not available.
Actually, the fact that some hard disk drivers get stuck in the boot
process when they try to access the SCSI chip of a TT emulated by Hatari
is a result of doing nothing. The hardware seems to be there (no bus
error), but things go wrong when software tries to access this hardware,
because it is not (fully) emulated.
In your case MiNT probably should check whether the SCC hardware is
present, and not do anything SCC-related if there is a bus error.
Best regards
Uwe