[Coco] V.BUSY: last question!

[Chuck Youse]

One last dumb question.

I see this in vrn.asm:

         ldb   PD.CPR,y   current process ID (can't depend on V.BUSY)

It's inside the GetStt code.  I'm wondering why this is; I was under the
impression the SCF/RBF serialized all access to the device drivers using
V.BUSY to synchronize various threads.  I.e., if you're in driver code,
V.BUSY is set and it's your process ID.

Is this an incorrect assumption?  Or are Getstt/Setstt exceptions to
this rule?

I suppose I could go digging through the code... just done _too much_ of
that lately, brain hemorrhaging.. 

C.