Just a suggestion but how about adding the header file to the Wiki and anyone who comes up with more info can throw it into it as well.. so everyone works from the same basic register sets...
Dave. so many cool things to do, not enough time :-) On Mon, 13 Sep 2004, Nicolai Haehnle wrote: > Hi, > > while I've had less success (read: hard locks and reboots) with the recently > drmtest and r300_demo, I did use glxtest to find out registers of the R300. > > Basically, what I did is run a small GL program, get the command buffer, > make some small changes and rerun. Often, this results in only a small > change in the command buffer (found using diff), which makes it possible to > guess register addresses and constants. So while I haven't been able to > crosstest my results by _sending_ commands using my new knowledge, I am > pretty certain that they are mostly correct (as long as there is no > explicit comment stating otherwise). > > So far, I have found registers for alpha blending and testing among other > things. I have also decoded most of the vertex program instruction set. > However, I do not have the registers for vertex program *setup* yet. All I > know is that both the program and its environment/parameters (whatever you > want to call it) are uploaded via 0x2208. > > All my findings are documented in the attached header file. > > cu, > Nicolai > -- David Airlie, Software Engineer http://www.skynet.ie/~airlied / airlied at skynet.ie pam_smb / Linux DECstation / Linux VAX / ILUG person ------------------------------------------------------- This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 Project Admins to receive an Apple iPod Mini FREE for your judgement on who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php -- _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
