Comment # 4
on bug 103544
from Roland Scheidegger
(In reply to Vitalii from comment #3) > (In reply to Emil Velikov from comment #1) > > Vitalii can you bisect Mesa to the commit that broke the game? There aren't > > many developer working on r600 - so this would be greatly beneficial. > > tell me how and what to do and I'll try git bisect is easy, albeit building 32bit mesa on a 64bit distro might be somewhere from challenging to near impossible depending on the distro... You just do git bisect start (probably on mesa master branch, but 17.2 branch should work too) git bisect good <sha id of a commit where things are working) git bisect bad <sha id of a commit where things are broken) build mesa, test (make sure testing really uses the newly compiled driver...) git bisect good (or bad), build, test, rinse and repeat...
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
