Yippie!

seen from China
seen from Italy
seen from Lebanon
seen from China

seen from China

seen from Singapore

seen from United States
seen from China
seen from China

seen from Malaysia

seen from Russia
seen from United States

seen from Malaysia
seen from United States

seen from United States

seen from United States

seen from Malaysia

seen from Singapore
seen from Belarus
seen from China
Yippie!

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
Time to get back to work on i68, I think. Next steps are as follows:
Continue clean up on i68soyuz. Top priority is to reorganize all the HAL stuff under src/system, src/z80 and src/68k into something more coherent, maybe combining the target-specific code into some kind of static library.
Second priority on i68soyuz is to stop trying to keep src/core "clean" of target-specific code when it hurts optimization. For example, the header files should include z88dk calling convention annotations where relevant, when the z80-specific preprocessor symbols are defined. (Maybe re-organize into src/core, with a "clean" C core; an src/native, with everything that's specific to i68 and a given target, like for example string constants; and src/system, with everything that's target-specific but not i68-specific, like keymatrix read routines? It's an idea.)
Finally, the rest of the general cleanup of i68soyuz. Lots of functions to move around.
Improve error-handling in i68soyuz.
Improve handshake procedure to include stuff like feature support, configuration details, etc.
Cleanup for i68apollo. For example, moving stuff like key translation tables into config files instead of the current system of bigass match statements.
Start actually implementing new features between the two, like being able to choose which key should be treated as 'break', a low-latency mode that prioritizes packet throughput over everything else, and the ability to automatically re-synchronize in case of packet loss, among other things.
Switch crates for uinput integration, I don't care for the one I'm using.
Write XKB definitions for the supported calculators. (Optional)
Also in there could I think be enabling a v200 target, I think it behaves identically to the TI-92 Plus where relevant.
Ughhhh. I should get back to work on my useless calculator bullhonkey. Gotta implement APD for the TI-83 Plus.
Deeply annoying that the default TI-89/92 Plus system timer autovector reads/writes to the bus. If I mask it while reading the keyboard matrix, the loop is too tight and the Automatic Power Down timer doesn't decrement; if I don't mask it, then AFAICT there's a chance it'll majorly corrupt both i68soyuz's state and the AMS' state. It hasn't happened in testing (yet) but I might need to go back to masking it and insert an artificial delay into the main loop. Or maybe move my key matrix reading code into autovector 1. Or maybe it's fine. IDK.
We've got keypresses!!!!

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
holy shit it built
Progressing on the TI-83 Plus port. I've written a couple little dummy programs to test out reading the keyboard, sending data over the link interface (like shown), manipulating text, etc. and I'm almost ready for a brittle all-up test. Gotta figure out how to register/unregister interrupt handlers first.
*Anakin returning to Palpatine after massacring the Jedi temple voice* it is done
I haven't even started the actual port yet--this is all just preparation for the port.
(Also I caved and went the sub-Makefile route. Yeah it duplicates a lot but it seemed easier.)