toxie
You may change this now in User CP
- Reaction score
- 50
Then back to the T3K deadlock issue..
One theory i have is the following: Could it be that due to the way the 'instantaneous' DMAs/Comms/etc work in Nuance, that T3K actually relies on these operations to take more cycles than 1?
So that the operations are executed too fast and thus the T3K code cannot react accordingly?
I wonder how one could fix/workaround this.
Add a queue that delays the signalling of certain operations?
Or delay the execution of certain commands by the spec'ed amount of cycles?
One theory i have is the following: Could it be that due to the way the 'instantaneous' DMAs/Comms/etc work in Nuance, that T3K actually relies on these operations to take more cycles than 1?
So that the operations are executed too fast and thus the T3K code cannot react accordingly?
I wonder how one could fix/workaround this.
Add a queue that delays the signalling of certain operations?
Or delay the execution of certain commands by the spec'ed amount of cycles?