> > I am hoping that the OGC card can route messages from the mainboard > > firmware to the OGC card's rs-232 port. That way you have a working > > console, which is useful for booting an OS (which device to boot from, > > what file to boot, what flags to add). From what I've been reading, > > the LinuxBIOS people would find this useful as well. > > It almost sounds like what you're asking for is the ability to watch > the 80x25 text framebuffer, scan it periodically for changes, and then > send that out via serial using vt100 codes so as to replicate what one > would see on the VGA screen.
If that is the easiest way for OGC to do it, it sounds like that would work. > How do we deal with the 24-line/25-line disparity? a) Use a terminal or terminal emulator with at least 25 lines. Or 24 lines plus a scroll buffer. Choose cursor movement commands that paint the screen properly if the screen is larger than 80x24. b) Look for a blank line and delete it. But this is more work and there might not be a blank line. c) Could simply paint the entire screen every time it changes and let the user watch the 1st line as it scrolls by. But this would not work with a display that constantly changes, like a clock, or a memory test that constantly updates the number of bytes tested. d) ??? Of these 3, I would go with (a). _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
