> > SCSI should be working on a TT (but someone should really try!) but causes
> > trouble on a Falcon (as in: it ate a filesystem of mine) at least when
> > used concurrently with IDE. I have the notion it's because locking of the
> > ST-DMA interrupt by IDE is broken in 2.6 (the IDE driver always complains
> > about trying to release an already-released ST-DMA). Needs more work, but
> > that's on the IDE or m68k interrupt side rather than SCSI.
>
> That driver really needs more work. Several things in it have become
> obsolete, e.g. it still uses sleep_on() and manages it's own queue.
Throw me a few more hints, please. I already knew about error handling
being changed; what should I use for sleep_on(), and will the driver still
be able to release the ST-DMA lock on request done if queue management is
done by the midlevel?
Michael
-
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
