27.04.2010 21:33, Daniel Mack пишет: > On Tue, Apr 27, 2010 at 09:27:15PM +0400, The Source wrote: > >> 27.04.2010 19:43, Daniel Mack пишет: >> >>> You would check out the latest mainline sources: >>> >>> $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git >>> $ cd linux-2.6 >>> >>> Then create a branch and merge the latest ALSA patches: >>> >>> $ git checkout -b alsa >>> $ git pull git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git >>> >>> Then build and install the kernel and verify it still shows the error. >>> Start the bisect and mark the current revision as 'bad': >>> >>> $ git bisect start >>> $ git bisect bad >>> >>> Assuming that v2.6.34-rc5 (before the merge) still works, you would mark >>> this as 'good': >>> >>> $ git bisect good v2.6.34-rc5 >>> >>> git will now iterate you thru the changes and drop you off at chosen >>> points. Just compile the tree you get, and tell git whether this is a >>> good or bad one: >>> >>> $ git bisect good >>> or >>> $ git bisect bad >>> >>> Then recompile and test again After some steps, it will tell you which >>> commit precisely broke it. >>> >>> HTH, >>> Daniel >>> >>> >>> >> I'll try that. But is there any way to do this just with alsa and >> not with entire kernel? Compiling kernel is a loooong process. >> > The description above won't touch much things outside the ALSA tree > during the bisect, so it shouldn't take long to compile. > > Thanks for helping, > Daniel > > > I'm sorry, but after 2 or 3 steps (of ~10) I got kernel that doesn't even boot properly (2.6.34-rc4, something with sata is broken) so I can't test my card with this kernel. Should I mark current version as bad and continue or something else can be done? _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
