|
|
|
@ -6,12 +6,16 @@ desires. |
|
|
|
* High level ideas |
|
|
|
|
|
|
|
the rust program has two threads, one is getting the inputs from $SOMEWHERE and |
|
|
|
the other is doing the file I/O to the game \\ |
|
|
|
the other is doing the file I/O to the game |
|
|
|
|
|
|
|
the game bridge thread has two file descriptors open, a fifo for feeding inputs |
|
|
|
to the game and a fifo opened by the game for signaling vblanks \\ |
|
|
|
to the game and a fifo opened by the game for signaling vblanks |
|
|
|
|
|
|
|
the game will then write a readiness signal to the rust program and read the |
|
|
|
button data fifo \\ |
|
|
|
then things will progress normally \\ |
|
|
|
button data fifo |
|
|
|
|
|
|
|
then things will progress normally |
|
|
|
|
|
|
|
the getting the input thread of the rust program will have some logic for |
|
|
|
telling how long ago it got liveness of the input source (explicitly vaguely |
|
|
|
defined to allow a controller to sit there and do nothing as long as it still |
|
|
|
|
