>> I actually need to know if bluetooth-next tree still has this issue. That is first and foremost the one thing that needs to be checked. > I asked Tim to mention the kernel version on x86 vs. the version on > ARM, because I vaguely remember this same issue being reported last > year (or even 2011) and being fixed (If I find the patch, I will let > you know). As Tim mentions later on, on x86 the issue does not happen > on 3.8, but it is present on 3.2 (and I suspect it will also be > present on 3.4 on x86 as well). I was going to say yesterday (until my computer suddenly died due to overheating): Can't it be assumed that it's okay in bluetooth-next since the issue seems to be gone with kernels > 3.4? I was trying to get a 3.4.67 kernel running on one ARM device but unfortunately I can't seem to get the bluetooth dongle to be recognized (something to do with the USB code, I suspect). It's probably still an issue, though, so I'd really appreciate if you managed to find that patch! -Tim -- 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
