stephen_usher wrote:This is why I was suggesting using a Pi to do the hard work and then give a standard, simplified interface to the QL side.
As for "hard work", the work of such a Raspi implementation has not been done. And why should someone be motivated to do it, while he could just run a QL emulator on the Raspi? Also note, that during Raspi boot, one would not be able to type.
If someone does it anyway, I propose PS/2 as standard. It is well documented, long established, and implemented on superHermes and Q68. It could also be of general use beyond the QL.
It's also obsolete and has been for 20 years. Getting new PS/2 peripherals is problematic at best. And again, you're concentrating purely on the keyboard (and maybe mouse) and not the plethora of other devices, such as printers, networking, storage etc.
Would waiting a couple of seconds for a stripped down Pi boot be so much of a problem? Remember it wouldn't be a full system, merely a kernel and the minimal number of processes required to handle the USB and interface to the QL side of things. No shells, no other daemons, no systemd, read-only filesystem.i.e. an embedded system device controller, as per the set-up for the ZX Spectrum Next.
P.S. Imagine being able to do something like this, for example:
And the Pi doing all the TCP/IP and TLS encrypton stuff and the QL side being given the decrypted stream of bytes.
Or, setting the default printer output to a networked printer with the Pi translating ESC/p encoded pages from Quill etc. into PCL5 or postscript.
For many things even a faster QL wouldn't have the horsepower to do these things. Better to let a dedicated peripheral controller do it and allow the QL side to do the things that it's best at.