Actually all #3 traps are implemented at the discretion of the device driver, so it's always just a documentation of what they should do, not necessarily of what they are actually doing ;-)
IOF.FLSH and IOF.CHEK don't make sense for RAM discs, for example, there is nothing to flush, it's all just in RAM anyway. So they just say "all right, did it" and be done with it. I for one don't think this needs to be mentioned separately. Cheers, Marcel Derek Stewart wrote: > Hi Wolfgang, > > Of course I mistaken said Section 5.3, when it should be Section 5.2 > > So the possible changes for Section 5.2 end Paragraph could read: > > <correction> > > The IOF.FLSH and IOF.CHEK commands are subtly different: IOF.FLSH > ensures that all write operations are complete, whereas IOF.CHEK ensures > that all write and read operations (including prefetches) are complete. > > Not all drivers will implement this trap, e.g. for ram disks where this > will just go to a MOVEQ 0,D0 and an RTS) > > </correction> > > Does > > Regards, > > Derek _______________________________________________ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
