> > All we need is support for the RD/RDP serial port.
> We can definitely do that (we expose configurable serial ports about 5 times before
> breakfast on the non-arcade side), but it'll completely shatter every frontend not
> named "qmc2" then.
I'm curious what this means. I'm not familiar with the front ends, nor the architecture issues.
I *think* you mean it breaks the front ends in the sense that they wouldn't have a clue how to start RDP if it required them to start three different instances of MAME and make each of them talk over a virtual serial port. Is that it?
If so, my thought would be to not do that. Keep RDP coded the way it is. Simply add two more targets. One could be RDP-center-only, the other would be RDP-side-only. Wanna use those two? No front end for you.
Allow them to talk to virtual or real serial ports. Add that same code to RD so it can link, too. Boom, problem solved. Or am I missing something?