Quote:
Originally Posted by Ether
You probably meant non-interruptible?
So if all the commands should be "non-interruptive", and non-interruptive means non-interruptible, then all new commands will fail to be scheduled if any command is presently running?
|
Yes, I meant non-interruptible.
And yes, the currently running command would have to end before any other command that requires the same subsystem could be scheduled. This is only true if you set the command's interruptible property to false.