You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is really more of a technical question than an "issue":
Looking at the schematics for both the graphics card and the vt100 terminal card, it looks like it would be relatively easy to combine the functionality of both cards into one, at least from an electrical point of view. Also, if designed to be compatible with the enhanced RC2014 bus or perhaps the unofficial BP-80 bus (such as that used by Stephen Cousins SC126, which is backward-compatible) it could tie the /WAIT pin straight into the bus as opposed to having a separate header pin for it.
But then there is the firmware. My first thought is you could send a command to switch between graphics mode and terminal mode. The board would start up in terminal mode by default, of course. Then a game or program that required graphics would send a command to enter graphics mode and before the program exited, it would have to restore terminal mode.
But I have no idea if that is something that is technically possible on the propeller in terms of firmware size or memory usage, etc.
The text was updated successfully, but these errors were encountered:
This is really more of a technical question than an "issue":
Looking at the schematics for both the graphics card and the vt100 terminal card, it looks like it would be relatively easy to combine the functionality of both cards into one, at least from an electrical point of view. Also, if designed to be compatible with the enhanced RC2014 bus or perhaps the unofficial BP-80 bus (such as that used by Stephen Cousins SC126, which is backward-compatible) it could tie the /WAIT pin straight into the bus as opposed to having a separate header pin for it.
But then there is the firmware. My first thought is you could send a command to switch between graphics mode and terminal mode. The board would start up in terminal mode by default, of course. Then a game or program that required graphics would send a command to enter graphics mode and before the program exited, it would have to restore terminal mode.
But I have no idea if that is something that is technically possible on the propeller in terms of firmware size or memory usage, etc.
The text was updated successfully, but these errors were encountered: