Rune Petersen wrote: > Hi, > > I finally managed to iron out the last issue with getting a fully > working fragment.position for the r300 driver. > > This should really require the big discussion if it wasn't for the fact > that it depends on functional changes in r300_vertexprog.c > (r300_select_vertex_shader4). > > The patches: > > r300_select_vertex_shader4: > The patch makes the vertex program output from the fragment input. It > makes the driver capable of catching output-input mismatches. primarily > based on some of Aapo Tahkola's code. > > > mesa-support_internal_driver_state_vars: > Makes it possible for driver to define its own internal state parameters.
Checked in. > r300_fragment_wpos5: > Adds fragment.position support, depends on the above patches. This patch doesn't apply cleanly to Mesa CVS head. r300_select_vertex_shader4.patch applies OK, but I'll hold off it until until the first one is resolved. -Brian ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
