Re: [hatari-devel] IDE IO register range access commit |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] IDE IO register range access commit
- From: Thomas Huth <th.huth@xxxxxxxxx>
- Date: Sun, 27 Sep 2020 09:27:18 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1601191639; bh=ue44w3C3QrxV7X4/CK9UGZz6kloyw+4gmWbAfxHgqdo=; h=Date:From:To:Subject:From; b=nxsuETxomnOnJm3YvH+h5uHtjO9nkRzmvrqNLmvk7vq0dyqw+58Ty6TDmJFNEuSyJ Trx9srafWUBTaO/MpYzfUNDB6T3XNLi2k+t0U7egTFKpbMVH6t/NkefmBzHfaC8fib /FTehic/Jjy/h7s89Dfz2lDEzG1iYMDVMa1KGKgQcjo1CXrxeDqXhFsYe3hF71qL6Y 1gLyztETluPERV7lx5SGW/L532ZVBq80vVIJaoTsrNDou0H1B5kr7ICIUuuGBUBWeY oR28MWJLgXe+OZp9/ra2Wn2aVLjw7ryYe8oilbTTrAs3G/LY+e7ztpDhngroYbKNHp TVaRUabt0Mm5g==
Am Sat, 26 Sep 2020 18:57:00 +0200
schrieb Uwe Seimet <Uwe.Seimet@xxxxxxxxx>:
> Hi,
>
> > I've now had a look, and I think I've successfully fixed the issue
> > reported by Uwe, and another crash that occurred when there was
> > only a secondary IDE drive attached, without a primary one.
> >
> > BTW, the hard disk driver Cecile now also seems to work fine in
> > Falcon mode when no IDE drive has been specified (it used to crash
> > with a bus error before) :-)
>
> The crash is gone, but strictly speaking there is still something
> wrong, or at least unusual:
>
> When I assign an IDE slave drive only, without master drive, the IDE
> interface is available and the slave drive is accessible. But a slave
> without master is not supported by IDE.
Honestly, that's also what I thought first. But apparently some hard
disk drivers can deal just nicely with that situation...
Also on https://en.wikipedia.org/wiki/Parallel_ATA they write:
"Master and slave clarification
[...] Since ATA-2 the two devices are referred to as "Device 0" and "Device 1", respectively. This is more appropriate since the two devices have always operated, since the earliest ATA specification, as equal peers on the cable, with neither having control or priority over the other.
It is a common myth that the controller on the device 0 drive assumes control over the device 1 drive, or that the device 0 drive may claim priority of communication over the other device on the same ATA interface. In fact, the drivers in the host operating system perform the necessary arbitration and serialization, and each drive's onboard controller operates independently of the other."
.... and that rather sounds like the secondary drive could also operate
without the primary one?
Thomas