Am 31.05.2014 08:45, schrieb Alexander Holler:
Am 31.05.2014 07:28, schrieb Marcel Holtmann:
so I actually wonder if we should move away from timer and move to a delayed
work item to handle the timeout and if that would actually fix this issue.
The problem is that I have absolutely no clue
Am 31.05.2014 07:28, schrieb Marcel Holtmann:
> Hi Alexander,
>
>> I assume the timeout for processing HCI commands was originally intended to
>> detect hung bluetooth devices and should not include the time needed locally
>> to handle the response to an HCI command. That is important because the
Am 31.05.2014 07:28, schrieb Marcel Holtmann:
Hi Alexander,
I assume the timeout for processing HCI commands was originally intended to
detect hung bluetooth devices and should not include the time needed locally
to handle the response to an HCI command. That is important because the time
Am 31.05.2014 08:45, schrieb Alexander Holler:
Am 31.05.2014 07:28, schrieb Marcel Holtmann:
so I actually wonder if we should move away from timer and move to a delayed
work item to handle the timeout and if that would actually fix this issue.
The problem is that I have absolutely no clue
Hi Alexander,
> I assume the timeout for processing HCI commands was originally intended to
> detect hung bluetooth devices and should not include the time needed locally
> to handle the response to an HCI command. That is important because the time
> needed locally (by the kernel or even
Hi Alexander,
I assume the timeout for processing HCI commands was originally intended to
detect hung bluetooth devices and should not include the time needed locally
to handle the response to an HCI command. That is important because the time
needed locally (by the kernel or even userland)
I assume the timeout for processing HCI commands was originally intended to
detect hung bluetooth devices and should not include the time needed locally
to handle the response to an HCI command. That is important because the time
needed locally (by the kernel or even userland) to process responses
I assume the timeout for processing HCI commands was originally intended to
detect hung bluetooth devices and should not include the time needed locally
to handle the response to an HCI command. That is important because the time
needed locally (by the kernel or even userland) to process responses
8 matches
Mail list logo
