From 1d0da2661faeecfe2352b44b132108304864bc57 Mon Sep 17 00:00:00 2001 From: Cadey Ratio Date: Fri, 8 May 2020 22:03:34 +0000 Subject: [PATCH] Update 'doc/gamebridge.org' --- doc/gamebridge.org | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) diff --git a/doc/gamebridge.org b/doc/gamebridge.org index 2c2ebcf..77c6c35 100644 --- a/doc/gamebridge.org +++ b/doc/gamebridge.org @@ -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