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 ------------------------------------------------------------------------------ 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
