| Re: [hatari-devel] ACSI: READ/WRITE (10) incorrectly evaluate block number |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/hatari-devel Archives
]
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] ACSI: READ/WRITE (10) incorrectly evaluate block number
- From: Uwe Seimet <Uwe.Seimet@xxxxxxxxx>
- Date: Sat, 26 Oct 2013 20:25:51 +0200
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; t=1382811951; l=481; s=domk; d=seimet.de; h=In-Reply-To:Content-Type:MIME-Version:References:Subject:To:From: Date:X-RZG-CLASS-ID:X-RZG-AUTH; bh=P/MOxwDZE6jnalQGwmNqqhr+hWM=; b=oe8DuiusTfHrM7Hhhd3KS/AxtJAyRLhybGDQJmhaCv8QOpEhh7w4RSCFeW0WpmbU+du xKPAmsz8yAUxczIgALUc+J+qaNa+AJ+4TzJ55MfEBKUtqI1pdwcKPtsdSstwfvJiHS8mE 9lbWfiGqXthi6X0XvnN4jLlzD6VZJm7yVwo=
> 1. READ CAPACITY (10) returns a wrong block count. My image has a size of
> 410009600 bytes, so it should have 800800 blocks of 512 bytes each.
By the way, I've just noticed that my IDE master drive image has the
same size as the ACSI drive image. So the values returned by READ
CAPACITY should be identical. 800800 would be correct. The ACSI value is
much too high, and the IDE value is a bit too low, even though this is
not a problem in practice.
Take care
Uwe