Short bump on this. I noticed Dave committed something that might fix this better, is everything working now? For some reason, r300c didn't break over here, so I can't really see whether everything's okay again.
~ C. 2010/2/3 Michel Dänzer <mic...@daenzer.net>: > On Tue, 2010-02-02 at 11:52 -0800, Corbin Simpson wrote: >> Module: Mesa >> Branch: master >> Commit: 3fedfc71289875de7e8381fb298aa26cee8d1822 >> URL: >> http://cgit.freedesktop.org/mesa/mesa/commit/?id=3fedfc71289875de7e8381fb298aa26cee8d1822 >> >> Author: Scott Moreau <ore...@gmail.com> >> Date: Tue Feb 2 11:59:53 2010 -0700 >> >> Track frag shader changes introduced by commit >> 4769566500be1a53dd9b4cc1a613aef439a0e3d8 >> >> Signed-off-by: Corbin Simpson <mostawesomed...@gmail.com> >> >> --- >> >> src/mesa/drivers/dri/r300/r300_blit.c | 2 +- >> 1 files changed, 1 insertions(+), 1 deletions(-) >> >> diff --git a/src/mesa/drivers/dri/r300/r300_blit.c >> b/src/mesa/drivers/dri/r300/r300_blit.c >> index e24c795..54ac251 100644 >> --- a/src/mesa/drivers/dri/r300/r300_blit.c >> +++ b/src/mesa/drivers/dri/r300/r300_blit.c >> @@ -114,7 +114,7 @@ static void create_fragment_program(struct r300_context >> *r300) >> inst->U.I.SrcReg[0].Swizzle = RC_SWIZZLE_XYZW; >> >> compiler.Base.Program.InputsRead = (1 << FRAG_ATTRIB_TEX0); >> - compiler.OutputColor = FRAG_RESULT_COLOR; >> + compiler.OutputColor[0] = FRAG_RESULT_COLOR; >> compiler.OutputDepth = FRAG_RESULT_DEPTH; >> compiler.is_r500 = (r300->radeon.radeonScreen->chip_family >= >> CHIP_FAMILY_RV515); >> compiler.code = &r300->blit.fp_code; > > Are you guys getting working hardware acceleration with this driver > since the compiler MRT changes? For me e.g. running > > RADEON_DEBUG=all ./progs/tests/fbotest1 > > prints out among other things: > > Fragment Program: Initial program: > # Fragment Program/Shader 0 > 0: MOV OUTPUT[1], INPUT[1]; > 1: END > Fragment Program: After native rewrite: > # Radeon Compiler Program > 0: MOV output[1], input[1]; > r300compiler error: get_used_ptr: index 256613760 is out of bounds for > file 3 > WARNING! Falling back to software for fragment program > > So only software rendering, presumably because OutputColor[1..3] aren't > initialized properly. I've tried initializing them to various values and > while some of them get me past the problem above, then I only get a > black window. > > The r300g driver is working though, including the drawbuffers(2) tests > these changes were aimed at. > > Any ideas? FWIW this is on my PowerBook with an RV350. > > > -- > Earthling Michel Dänzer | http://www.vmware.com > Libre software enthusiast | Debian, X and DRI developer > -- Only fools are easily impressed by what is only barely beyond their reach. ~ Unknown Corbin Simpson <mostawesomed...@gmail.com> ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
