On 08/03/2009 04:02 PM, Roland Scheidegger wrote: > On 03.08.2009 16:50, Terry Barnaby wrote: >> On 08/03/2009 03:38 PM, Roland Scheidegger wrote: >>> On 03.08.2009 14:00, Terry Barnaby wrote: >>>> I have done some "git bisecting" of the mesa source code under Fedora 11 >>>> as the >>>> base platform and with an ATI M22 [Mobility Radeon X300]. >>>> The code at mesa_7_4 is good and works with F11. >>>> The code at mesa_7_5 is bad. >>>> >>>> I have found that the bug seems to appear at: >>>> 5340b6dff73a0a23531ce2a5f28fba8303adab6e (Merge commit >>>> 'origin/gallium-master-merge') >>>> >>>> This looks like a major gallium merge into the main trunk ?? >>>> >>>> The code at: 9fd26daec24f21dbe17afcb2e2ab272667ee9a69 (mesa: remove the >>>> unused >>>> _mesa_UpdateTexEnvProgram() function) appears to run fine on my system. >>>> >>>> I have tried to bisect the bug through the >>>> ee4c921b65fb76998711f3c40330505cbc49a0e0 (Merge commit 'origin/gallium-0.2' >>>> into gallium-master-merge) branch, but it gets difficult here due to dri >>>> drivers not being built by default, different drm/dri version requirements >>>> and >>>> different build systems. >>>> I will try a bit more here. >>>> Any info on the "origin/gallium-master-merge", it looks like this was >>>> separated >>>> before mesa_7_0 ? >>> You probably can't really track that through gallium branches. >>> And yes gallium branched off from master befroe mesa_7_0. >>> That said, if the bug is caused by the merge, it might (or not) be >>> feasible to look at differences between before and after merge - >>> certainly that's a gigantic diff, but almost all of the diff should be >>> in only gallium-relevant files, not needed for old drivers and core mesa >>> at all. >>> >>> Roland >> Yes, I have started looking at the differences. >> However, there are quite a large number of changes to the r300 dri driver >> as well as the rest of the code. So some work on the r300 dri driver was done >> in this branch for some reason ... > Really? I tried that here and I saw zero difference in the r300 driver > (though there was one with initialization for radeon which would also be > relevant for r300). The gallium r300 driver isn't relevant for this. > There was no development done in gallium branch on r300 driver, though > master branch was merged to gallium some times so depending what exactly > you're looking at you might see these differences too (I just did git > diff -p between those 2 commits and got no changes for r300 but some for > core mesa). > > Roland Ok, I have probably got something wrong here then. I will try and see why I see a large set of differences ...
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
