@Jose
Programming efficient code for existing 680x0+PPC cards is quite interesting :-)
You can do a lot of os calls if you are careful - Design the code such that OS calls can be gathered together, create a 680x0 function that handles these OS calls and do a manual context switch to that function.
As an example I wrote a small test context in C that maintains a double buffered screen and handles input. I wrote it in vbcc-wos/68k to test the idea of manual switches on performance.
When I refresh, a 68K function is called. This function does the buffer flip and gathers and processes all the pending idcmp messages since the last frame (well up to a certian amount) into a pair of mouse / key data buffers. This included stuff like KeyMap based raw key mapping. So there were quite a few OS calls there.
The code then switches back to PPC and the input buffers are processed by PPC callback functions before the refresh() function finally returns.
So for the price of 2 complete context switches (PPC->68K->PPC) we get our buffer flipped, synchronised and the input ready to use by the PPC.
Hmm, I have wandered off topic again, havent I? Sorry, must be the late hour :-)
It worked quite well :-)