Re: HID UNPLUG_VIRTUAL_CABLE event issue

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Luiz,
I mean we may send the virtual cable unplug event before we disconnect
the L2CAP link, should it comply to the spec more?
Best regards
shy



2011/8/23 Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx>:
> Hi,
>
> On Tue, Aug 23, 2011 at 11:54 AM, shy <shyboysby@xxxxxxxxx> wrote:
>> Hi Marcel,
>> According to connection_disconnect in input/device.c(Bluez version
>> 4.93), it would disconnect INTR and CONTROL L2cap link and then send
>> HIDP_CTRL_VIRTUAL_CABLE_UNPLUG message by the process sequence.
>> That seems it doesn't comply to the spec Page120, HID version 1.0.
>> Could you please confirm this case? If so, I would submit a patch.
>
> You mean that the disconnect sequence is wrong? Note that we only send
> virtual cable unplug in case the device is being removed, otherwise it
> is just a regular disconnect.
>
>
> --
> Luiz Augusto von Dentz
>
--
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


[Index of Archives]     [Bluez Devel]     [Linux Wireless Networking]     [Linux Wireless Personal Area Networking]     [Linux ATH6KL]     [Linux USB Devel]     [Linux Media Drivers]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Big List of Linux Books]

  Powered by Linux