On 11/16/06, Rune Petersen <[EMAIL PROTECTED]> 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. > > r300_fragment_wpos5: > Adds fragment.position support, depends on the above patches. > > > Any questions/ideas/comments/??, I am all ears. > > > > Rune Petersen > > > P.S. > Brian, Roland, Keith, thank you for your patient replies. >
I can't comment on the mesa part (not familiar enought with that) otherwise i think your patch is good. Neverless i got the feeling that this vertex/fragprog input/output match maybe usefull to other driver in the future, maybe it would have been better to push that into mesa. One more things iirc Keith did somethings in mesa about position invariant and vertex program, can't remember exactly as i wasn't much looking in vertex shader at that time :) Anyway good job Rune :) best, Jerome Glisse ------------------------------------------------------------------------- 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
