diff options
author | Sven Schnelle | 2019-11-01 17:55:13 +0100 |
---|---|---|
committer | John Snow | 2020-03-27 19:30:08 +0100 |
commit | 9e58f172700a3fc56fd6c97d033efa8ade51c9ce (patch) | |
tree | 66adff16809ae427a6740601ed13ef5cb0733ea7 /migration/multifd-zlib.c | |
parent | Merge remote-tracking branch 'remotes/vivier2/tags/linux-user-for-5.0-pull-re... (diff) | |
download | qemu-9e58f172700a3fc56fd6c97d033efa8ade51c9ce.tar.gz qemu-9e58f172700a3fc56fd6c97d033efa8ade51c9ce.tar.xz qemu-9e58f172700a3fc56fd6c97d033efa8ade51c9ce.zip |
fdc/i8257: implement verify transfer mode
While working on the Tulip driver i tried to write some Teledisk images to
a floppy image which didn't work. Turned out that Teledisk checks the written
data by issuing a READ command to the FDC but running the DMA controller
in VERIFY mode. As we ignored the DMA request in that case, the DMA transfer
never finished, and Teledisk reported an error.
The i8257 spec says about verify transfers:
3) DMA verify, which does not actually involve the transfer of data. When an
8257 channel is in the DMA verify mode, it will respond the same as described
for transfer operations, except that no memory or I/O read/write control signals
will be generated.
Hervé proposed to remove all the dma_mode_ok stuff from fdc to have a more
clear boundary between DMA and FDC, so this patch also does that.
Suggested-by: Hervé Poussineau <hpoussin@reactos.org>
Signed-off-by: Sven Schnelle <svens@stackframe.org>
Reviewed-by: Hervé Poussineau <hpoussin@reactos.org>
Diffstat (limited to 'migration/multifd-zlib.c')
0 files changed, 0 insertions, 0 deletions