https://bugzilla.kernel.org/show_bug.cgi?id=93911 --- Comment #10 from Azael Avalos <coproscefalo@xxxxxxxxx> --- (In reply to HLJonker from comment #9) > I'd love to check! > I'm sorry to say that I am more than a little green behind the ears when it > comes to kernel hacking though: no clue where to find the commits, no clue > how to test them. NP, just follow the links I provided below :-) commit 5d3fc1d54e5a020c087002dd8590ee21c17e3182: https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/plain/drivers/platform/x86/toshiba_bluetooth.c?id=5d3fc1d54e5a020c087002dd8590ee21c17e3182 commit d85b11b1a4bee3146540111ef15b5ca1eeb71645: https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/plain/drivers/platform/x86/toshiba_bluetooth.c?id=d85b11b1a4bee3146540111ef15b5ca1eeb71645 > I'm guessing I'd somehow need to 1) acquire a kernel built with these > commits, and then 2) install the kernel; 3) reboot into the modified kernel > and 4) check if the problem has gone away (and if bluetooth other than that > works). > > Could you give some pointers on how to do 1 / 2? I'm guessing that if I can > get it installed as "TEST-KERNEL" and run an update-grub, I can find it on > booting. There's no need to recompile the whole kernel, just use the Makefile I provided earlier (comment #2), and replace the file with the ones from the links, each at a time of course. Basically: - Download the Makefile (comment #2) if not already downloaded - Download the file from 1st link - make clean - make - sudo make install - sudo make load - test ;-) - Repeat for 2nd link Cheers Azael -- You are receiving this mail because: You are the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
