|[hatari-devel] (Missing) TT SCSI emulation problems|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: [hatari-devel] (Missing) TT SCSI emulation problems
- From: Uwe Seimet <Uwe.Seimet@xxxxxxxxx>
- Date: Sun, 23 Aug 2015 20:18:10 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1440353890; l=771; s=domk; d=seimet.de; h=Content-Disposition:Content-Type:MIME-Version:Subject:To:From:Date; bh=lI85GfkNG61+f4Gy+I6azF/FnL280mgTo9janKVb3KU=; b=IgVnrCzQVs+B+TluMTFVsH8a1jrzazfcs+p1Z0i6bivIzCYEoT4eKDABvMqcPOpZsT3 s5ro9IK8Tm8dG+T4ON7EkzhO+/07iXOwiDKYsSYFeTddy1MF+ZxC5MqkOtPd5w1w5zC5o zqJnUCVJ7vX44uMQq7n7hUNBOqORubCGXSQ=
In the TT emulation, when launching HDDRIVER or CBHD in their default
configurations both drivers take a very long time to initialize. CBHD
even seems to be hanging forever. This is because they try to access the
TT's SCSI chip and even though this chip is not (at all?) supported by
Hatari, there does not seem to be a bus error when accessing its registers.
As a result the drivers assume TT SCSI is supported, they try to test for
devices and are blocked in some timeout loops.
I guess there is a reason why the TT emulation does not just throw a bus
error as long as the SCSI chip is not emulated. Why is this so, and what
about a startup (command line is sufficient) option that disables the
SCSI chip emulation in TT mode?