Re: [Qemu-devel] [PATCH] LSI53C895A: Do not update current_dma_len with dbc in TIA mode

[Justin Chevrier <theburner1@yahoo.com>]

> Even in Table indirect access, we update dbc after fetching
> the transfer
> count (TC) from the table.  The tech manual is unclear
> about whether or
> not dbc is updated:
> 
>     "For a MOVE instruction, the 24-bit byte count is
> fetched
>     from system memory. Then the 32-bit physical address is
>     brought into the LSI53C895A. Execution of the move
>     begins at this point" - LSI53C895A Tech manual,
> page 230.
> 
> However, I think in practice, it would have to do so.
> 

It is true that we update the dbc with the length acquired from the table. Unfortunately it seems the length acquired from the table is incorrect. Here are snippets of log from the Debian Arm target with current head.

We get a command complete with data ready, length 69632. current_dma_len is updated with this value:

lsi_scsi: MSG IN 0x80
lsi_scsi: MSG IN 0x20
lsi_scsi: MSG IN 0x07
lsi_scsi: Data ready tag=0x10007 len=69632

Then when we issue the TIA block move command the length at the table entry referenced is wrong (at 4096). The DBC gets updated with this new incorrect length, which then overwrites dma_current_length and we only transfer 4096 bytes.
lsi_scsi: SCRIPTS dsp=50000780 opcode 11000000 arg 000002e8
lsi_scsi: DMA addr=0x0000c000 len=4096
lsi_scsi: Command complete sense=0

With the patch sent today and how it behaved before my previous patch the code continues to use an unaltered current_dma_len (which stays at 69632).

It seems that the DSA + offset is pointing to the wrong table entry. I'm looking into this now.

I just wanted to get this patch out to fix breakages introduced by my original patch.

Justin