Adam Myrow, le Mon 05 May 2008 17:34:24 -0500, a ?crit : > I have found that as of yesterday, the Dectalk Express driver is > completely broken. > So, I reverted back to the stock speakup.s, and patched in the > older release of Speakup that it came with. This was dated 4/16/08. Well, it would be helpful if you could help tracking the bug :) You can track down the precise commit that broke it quite easily by using git bisect and compile as modules: git checkout master # to get to current version git bisect start git bisect bad # to tell that the current version is bogus git log # to find a good-looking version git checkout 2a2840d1c6a8c2f2742c469bf1736348bc124c28 cd src/ make sudo insmod speakup.ko sudo insmod speakup_dectlk.ko start=1 # check that that version does work sudo rmmod speakup_dectlk sudo rmmod speakup cd .. git bisect good # to tell that that version does work And from then on, git will let you try the intermediate versions by dichotomy: the last "git bisect good" command has actuallay checked out an intermediate version, which you can test by the same sequence as above: cd src/ make sudo insmod speakup.ko sudo insmod speakup_dectlk.ko start=1 # check whether that version does work sudo rmmod speakup_dectlk sudo rmmod speakup cd .. Here you have tested the intermediate version, and you can run either git bisect good or git bisect bad to give the result, and git will check out a yet more refined intermediate version, which you can test, etc. until git eventually tells you exactly which commit did bring the bug, and then it will be a lot easier for us to check why. That being said, I suggest you first try the successive versions 2a2840d1c6a8c2f2742c469bf1736348bc124c28 533aa9b618cfc9d7460c811191bc30b87ada12c8 383be28905bd2e01107050a87675c5fec551d4cc as well as the successive versions e2801fc639fab12da08270b999c72e00da3c4607 a3966adfdca87e3089cb49b904b04dac961fe1aa Because we already know that these have been quite massive changes. Samuel
