In the end I used a chroot to do the cross-compiling. I think I successfully found the "bad commit" with git bisect so I've cross-posted the result to this bug and linux-wireless. I was a bit puzzled by git bisect though because it seemed to be getting versions/tags out of order. For example, I found a commit after tag 2.6.34 to be "good", but eventually I homed in on 2.6.33. Is that normal, perhaps because they originated from different branches which were merged apparently out of order?
-- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org