> In the flags there are 2 bits. One is tested for by the current TARGET_TO_HOST
>macro, the other is tested for by the current
> HOST_TO_TARGET macro.
Not exactly. TARGET_TO_HOST is 1 bit (bit 3), HOST_TO_TARGET are 2 bits
(bit 3,4).
> To accomplish that I just thought of it as: As long as you don't
> specifically specify a transfer in the opposite direction, you want to
> transfer the data. So instead of checking for TARGET_TO_HOST, you check
> to make sure that HOST_TO_TARGET was /not/ specified, and instead of
> checking for HOST_TO_TARGET, you check to make sure that TARGET_TO_HOST
> was /not/ specified.
> Like I said, I have no idea if that is correct, but that may be an easier
> way to do it than checking for every possible case.
We should not confuse the SCSI subsystem. Your approach certainly will.
> And I'm definitely glad to see other people hammering on the code. ASPI
> is very cool because it is the first step to actually using Wine to support
> a piece of hardware (like a CD-R or DVD). Although in a way, a DVD
> player/CD-R program is not really a hardware interface, it's more of an
> application, and thus more along the lines of what Wine does.
Not really, several people already use the serial comm interface to talk
to digital cameras, and the parallel port stuff to talk parallel devices.
Ciao, Marcus
