On Fri, Feb 28, 2014 at 03:10:41PM +0100, Luiz Augusto von Dentz wrote: > Hi Adam, > > On Fri, Feb 28, 2014 at 1:22 PM, Anderson Lizardo > <anderson.lizardo@xxxxxxxxxxxxx> wrote: > > Hi Adam, > > > > On Fri, Feb 28, 2014 at 3:31 AM, Adam Lee <adam8157@xxxxxxxxx> wrote: > >> connect_dbus() fails sometimes with Intel 7260 bluetooth, sleeping 0.5s > >> before executing bluetoothd workarounds it. I assume the firmware > >> patching slows down hardware initialization then fails to connect. > >> > >> Any other possibility? I'm not a D-Bus guru :) > > > > Please provide more details, e.g. the bluetoothd logs showing the > > problems, btmon output and which steps you are using to reproduce it. > > If you are using bluetoothctl, tell us which commands you are using. > > My guess is that either your driver is not using .setup hook to do the > firmware patching or it is returning before it has fully initialize > the hardware, so please also add more information what is happening on > the driver side. Hi, all Please check https://bugs.launchpad.net/bugs/1221618 It's already fixed in btusb. However, if it's related to initialization as Luiz and I guessed, maybe other hardwares have this issue too, that's the reason I submitted that harmless retry "workaround" into BlueZ. (have no objection to NAK) -- Adam Lee http://adam8157.info -- 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
