Hi Luiz, On Sun, Feb 21, 2010, Luiz Augusto von Dentz wrote: > While discussing this problem we find out that our timeout doesn't > really work as we imagine due to the possibility of abort being > rejected, so either we don't call any callback on timeout and do it on > abort response while changing to aborting state (which probably means > 4-8 sec before we are really able to abort/cancel) or we disconnect as > the other end seems to not cooperate on aborting. > > Btw, we probably should have a smaller timeout for avdtp_abort anyway > and make sure we call it upon RequestDisconnect not avdtp_close which > has no priority over the others commands. Makes sense. Feel free to propose a patch (or multiple patches) for all this ;) Johan -- 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
