On Tue, Sep 23, 2008 at 7:04 AM, Mark Marshall <[EMAIL PROTECTED]> wrote: > Hi. > > I've just checked in a simple BIOS. It only really supports text modes 0 - > 3, and still has a few bugs in those. It uses the standard VGA registers > and knows nothing about OGD1. I've tested it with bochs, and I can boot DOS > - things seem OK.
Very nice! You're getting ahead of us, so the rest of us are going to have to figure out how to come to your aid on this. > > The README.txt file describes how to build and test it. > > What should I do next? > > I really want to know what would help out other people most. > - I can continue writing the BIOS blind, and hope that it works. > (This will happen in the background anyway, I can't > help but to tinker). Unfortunately, a fair amount of that has to happen. What I'd really like to do is get you a prototype card. The problem is that we don't have the HQ microcode ready for that. Would you be interested in that? > - I can write a plugin for bochs that simulates the OGD1 in C (C++) > I can see that there is a simulator or the advanced (3D) parts > of the OG project, but there's not a register level sim written > in C yet - does anyone think this is of value? This will make > writing the drivers easier as well, but it assumes we manage to > make the simulator match the verilog (which is hard - I know > that getting the simulated verilog to match ASIC verilog is > non-trivial) Honestly, it would be smart if we did have a C version of the code that does the translation. I've posted bits of it on the list. We can work out the details of the algorithm. Oh, and we'll need an 8x16 font. What I'm going to do right now is try to turn what I have into something that can actually compile, then I'll post it to the list. > - I can see if I can write a plugin for bochs that > interfaces with the verilog simulator. > I'm not sure which parts of the verilog would be needed for > this - I would really need some guidance as to which files > to try to include. We may need this later. Right now, you need a C model because it's more efficient for you to work with. I'll get you the translator today, and we'll have to work out the I/O address stuff as we go along. There is lots of info on this on the OGP wiki, and the more of us that are intimately familiar with it the better. > - I can try anything else that's needed really. > > I've also been playing around with a simple text database file that > describes the registers and a script that generates .v, .h and .inc files > from this data base. I also mean to produce .html (this sort of thing is V. > useful). Are people interested in this? I think it would be wonderful. We need more documentation. Thanks for your help! -- Timothy Normand Miller http://www.cse.ohio-state.edu/~millerti Open Graphics Project _______________________________________________ Open-graphics mailing list [email protected] http://lists.duskglow.com/mailman/listinfo/open-graphics List service provided by Duskglow Consulting, LLC (www.duskglow.com)
