Hi.

After a long absence, I now have a new PC. I have also written a rough framework for a VGA BIOS. It is very far from complete, but I'd like to show that I've done something and get some feedback on it.

I'm new to Open Source development, so this is very exciting (I have to tell myself that otherwise it would be just like being at work).

At the moment I set-up the registers for mode 0x03 and support a couple of other BIOS calls - most notably int 0x10, function 0x0E (which is what DOS uses to print a character). Almost everything else is still TODO.

The README.txt describes how to build and test.  Using Bochs has been easy.

I think that I've organised my time now so that I should be able to spend a few hours a week on this, so hope to start making faster progress.

I've attached a diff, generated by svn. I assume that this is the correct thing to do? This is my first go with svn, I've used CVS a long time ago, and use perforce at work. Can I request SVN commit access at some point, that would make things a bit easier.

There are a few things that I would like to change in the future. Although I don't yet access any OGD specific registers, I have written a .inc file that gives their addresses. This is the wrong thing to do. I would like to make a text file that fully describes every register in the card, and then have some perl / python that processed that file and produced all of include files for every part of the system. This would include verilog files for the RTL and html/pdf files for documentation. Bitter experience has taught me that this is a really good idea.

MM

PS.
I think I'm supposed to sign this?

I am the Originator of the attached code.
I give my permission for it to be copyrighted and licensed under the Traversal dual license agreement.
Signed by Mark Marshall.

Attachment: patch01.txt.gz
Description: GNU Zip compressed data

_______________________________________________
Open-graphics mailing list
[email protected]
http://lists.duskglow.com/mailman/listinfo/open-graphics
List service provided by Duskglow Consulting, LLC (www.duskglow.com)

Reply via email to