summaryrefslogtreecommitdiffstats
path: root/include/hw/ppc
diff options
context:
space:
mode:
authorAlexander Graf <agraf@suse.de>2013-06-28 13:30:01 +0200
committerAlexander Graf <agraf@suse.de>2013-07-11 18:51:25 +0200
commit80fc95d8bdaf3392106b131a97ca701fd374489a (patch)
treecc2c5277f074224385ee19e9066fca8ab56cd339 /include/hw/ppc
parentcae323572eddc1a45e2f6ef98c006d98fed23b1e (diff)
downloadhqemu-80fc95d8bdaf3392106b131a97ca701fd374489a.zip
hqemu-80fc95d8bdaf3392106b131a97ca701fd374489a.tar.gz
PPC: dbdma: Support unaligned DMA access
The DBDMA engine really just reads bytes from a producing device (IDE in our case) and shoves these bytes into memory. It doesn't care whether any alignment takes place or not. Our code today however assumes that block accesses always happen on sector (512 byte) boundaries. This is a fair assumption for most cases. However, Mac OS X really likes to do unaligned, incomplete accesses that it finishes with the next DMA request. So we need to read / write the unaligned bits independent of the actual asynchronous request, because that one can only handle 512-byte-aligned data. We also need to cache these unaligned sectors until the next DMA request, at which point the data might be successfully flushed from the pipe. Signed-off-by: Alexander Graf <agraf@suse.de>
Diffstat (limited to 'include/hw/ppc')
-rw-r--r--include/hw/ppc/mac_dbdma.h3
1 files changed, 3 insertions, 0 deletions
diff --git a/include/hw/ppc/mac_dbdma.h b/include/hw/ppc/mac_dbdma.h
index 4d7318d..90efd27 100644
--- a/include/hw/ppc/mac_dbdma.h
+++ b/include/hw/ppc/mac_dbdma.h
@@ -39,6 +39,9 @@ struct DBDMA_io {
DBDMA_end dma_end;
/* DMA is in progress, don't start another one */
bool processing;
+ /* unaligned last sector of a request */
+ uint8_t remainder[0x200];
+ int remainder_len;
};
/*
OpenPOWER on IntegriCloud