Hi Lizardo, On Tue, May 15, 2012 at 4:15 PM, Anderson Lizardo <anderson.lizardo@xxxxxxxxxxxxx> wrote: > Hi Mikel, > > On Mon, May 14, 2012 at 11:34 AM, Mikel Astiz <mikel.astiz.oss@xxxxxxxxx> wrote: >> From: Mikel Astiz <mikel.astiz@xxxxxxxxxxxx> >> >> MGMT_EV_DEVICE_DISCONNECTED should expose the disconnection reason to >> userland. > > There is "getsockopt(sock, SOL_SOCKET, SO_ERROR, &sk_err, &len)". Why > is it not enough? Could you please be more specific? Which socket type exposes this disconnect reason? That would be the second approach explained in the cover-letter (userspace part), but AFAIK it's not been set by the Kernel right now. We would probably have to set the option for all RFCOMM, L2CAP and SCO sockets associated to the ACL link. Cheers, Mikel -- 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
