-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Michel Dänzer wrote: > On Thu, 2008-09-25 at 01:24 +0200, Dieter Nützel wrote: >> example: >> >> Tunnel V1.5 >> Written by David Bucciarelli ([EMAIL PROTECTED]) >> Mesa 7.3-devel implementation error: >> radeon_program_pair.c::allocate_input_registers(): Don't know how to handle >> inputs 0x8 >> >> >> Please report at bugzilla.freedesktop.org >> pc=0************************************* >> Hardware program >> ---------------- >> NODE 0: alu_offset: 0, tex_offset: 0, alu_end: -1, tex_end: -1, flags: >> 00000000 >> *********************************WARN_ONCE********************************* >> File r300_render.c function r300Fallback line 366 >> Software fallback:!fp->translated >> *************************************************************************** >> Mesa 7.3-devel implementation error: >> radeon_program_pair.c::allocate_input_registers(): Don't know how to handle >> inputs 0x8 > > According to git bisect: > > 19d77d6cfa384142cc6ab4d9b3db4b28cefb6f19 is first bad commit > commit 19d77d6cfa384142cc6ab4d9b3db4b28cefb6f19 > Author: Brian <[EMAIL PROTECTED]> > Date: Tue Sep 18 19:29:26 2007 -0600 > > temporarily set the FRAG_BIT_FOGC bit in InputsRead when fog is enabled > (cherry picked from commit 63be96bdc7e9f388a5c49295bd7e150462fd003a) > > > The attached patch gets tunnel running here, but it still complains: > > *********************************WARN_ONCE********************************* > File r300_state.c function r300SetupRSUnit line 1756 > Don't know how to satisfy InputsRead=0x00000008 > *************************************************************************** > > > I think FRAG_BIT_FOGC needs to be handled in a couple of other places as > well, but I'll leave that to Corbin or Nicolai or so. :)
Did you cherry-pick that patch from my radeon-fog-coord branch? :3 Yeah, as you guys may have noticed, fixing fog coords in one place tends to badly break it in other places. I think the entire fog handling system for r300 needs to be scrubbed and re-written. Gallium will be nicer in this regard, since all fog will be shader-driven, IIRC. It would be *really* nice if AMD happened to know the magic numbers for getting the HW fog to behave exactly like OpenGL fog. *wink, wink* ~ C. - -- ~ Corbin Simpson <[EMAIL PROTECTED]> -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkjbtEsACgkQeCCY8PC5utA5xQCfcHxAJttThj5nH0HKjvXRxGDk QKgAn2ox9pZs+Wc6xs7+Ahtw91VC2ZjV =EmfO -----END PGP SIGNATURE----- ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ -- _______________________________________________ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
