Hi Alexander,
>>> The reasoning to do this is the following:
>>>
>>> - If a timeout occurs, the HCI-communication is broken afterwards and the
>>> dongle isn't usable anymore.
>>> - If it works after e.g. waiting 4s everyone is still happy but if it
>>> just breaks after only waiting 2s nothing
Am 31.05.2014 07:32, schrieb Marcel Holtmann:
> Hi Alexander,
>
>> The reasoning to do this is the following:
>>
>> - If a timeout occurs, the HCI-communication is broken afterwards and the
>> dongle isn't usable anymore.
>> - If it works after e.g. waiting 4s everyone is still happy but if it
Am 31.05.2014 07:32, schrieb Marcel Holtmann:
Hi Alexander,
The reasoning to do this is the following:
- If a timeout occurs, the HCI-communication is broken afterwards and the
dongle isn't usable anymore.
- If it works after e.g. waiting 4s everyone is still happy but if it
just breaks
Hi Alexander,
The reasoning to do this is the following:
- If a timeout occurs, the HCI-communication is broken afterwards and the
dongle isn't usable anymore.
- If it works after e.g. waiting 4s everyone is still happy but if it
just breaks after only waiting 2s nothing is gained.
-
Hi Alexander,
> The reasoning to do this is the following:
>
> - If a timeout occurs, the HCI-communication is broken afterwards and the
> dongle isn't usable anymore.
> - If it works after e.g. waiting 4s everyone is still happy but if it
> just breaks after only waiting 2s nothing is gained.
Hi Alexander,
The reasoning to do this is the following:
- If a timeout occurs, the HCI-communication is broken afterwards and the
dongle isn't usable anymore.
- If it works after e.g. waiting 4s everyone is still happy but if it
just breaks after only waiting 2s nothing is gained.
-
Am 16.05.2014 07:35, schrieb Alexander Holler:
Am 15.05.2014 17:19, schrieb Alexander Holler:
Am 15.05.2014 16:50, schrieb Alexander Holler:
Am 15.05.2014 14:54, schrieb Luiz Augusto von Dentz:
This timeout seems arbitrary so I suppose we can increase it if we
feel it is necessary but we
Am 16.05.2014 07:35, schrieb Alexander Holler:
Am 15.05.2014 17:19, schrieb Alexander Holler:
Am 15.05.2014 16:50, schrieb Alexander Holler:
Am 15.05.2014 14:54, schrieb Luiz Augusto von Dentz:
This timeout seems arbitrary so I suppose we can increase it if we
feel it is necessary but we
Am 15.05.2014 17:19, schrieb Alexander Holler:
Am 15.05.2014 16:50, schrieb Alexander Holler:
Am 15.05.2014 14:54, schrieb Luiz Augusto von Dentz:
This timeout seems arbitrary so I suppose we can increase it if we
feel it is necessary but we used already different timeout for
different
Am 15.05.2014 16:50, schrieb Alexander Holler:
Am 15.05.2014 14:54, schrieb Luiz Augusto von Dentz:
This timeout seems arbitrary so I suppose we can increase it if we
feel it is necessary but we used already different timeout for
different commands like HCI_POWER_OFF_TIMEOUT, so perhaps if we
Am 15.05.2014 14:54, schrieb Luiz Augusto von Dentz:
> Hi Alexander,
>
> On Wed, May 14, 2014 at 5:00 PM, Alexander Holler
> wrote:
>> The reasoning to do this is the following:
>>
>> - If a timeout occurs, the HCI-communication is broken afterwards and the
>> dongle isn't usable anymore.
>>
Hi Alexander,
On Wed, May 14, 2014 at 5:00 PM, Alexander Holler wrote:
> The reasoning to do this is the following:
>
> - If a timeout occurs, the HCI-communication is broken afterwards and the
> dongle isn't usable anymore.
> - If it works after e.g. waiting 4s everyone is still happy but if
Hi Alexander,
On Wed, May 14, 2014 at 5:00 PM, Alexander Holler hol...@ahsoftware.de wrote:
The reasoning to do this is the following:
- If a timeout occurs, the HCI-communication is broken afterwards and the
dongle isn't usable anymore.
- If it works after e.g. waiting 4s everyone is
Am 15.05.2014 14:54, schrieb Luiz Augusto von Dentz:
Hi Alexander,
On Wed, May 14, 2014 at 5:00 PM, Alexander Holler hol...@ahsoftware.de
wrote:
The reasoning to do this is the following:
- If a timeout occurs, the HCI-communication is broken afterwards and the
dongle isn't usable
Am 15.05.2014 16:50, schrieb Alexander Holler:
Am 15.05.2014 14:54, schrieb Luiz Augusto von Dentz:
This timeout seems arbitrary so I suppose we can increase it if we
feel it is necessary but we used already different timeout for
different commands like HCI_POWER_OFF_TIMEOUT, so perhaps if we
Am 15.05.2014 17:19, schrieb Alexander Holler:
Am 15.05.2014 16:50, schrieb Alexander Holler:
Am 15.05.2014 14:54, schrieb Luiz Augusto von Dentz:
This timeout seems arbitrary so I suppose we can increase it if we
feel it is necessary but we used already different timeout for
different
The reasoning to do this is the following:
- If a timeout occurs, the HCI-communication is broken afterwards and the
dongle isn't usable anymore.
- If it works after e.g. waiting 4s everyone is still happy but if it
just breaks after only waiting 2s nothing is gained.
- Having to wait some
The reasoning to do this is the following:
- If a timeout occurs, the HCI-communication is broken afterwards and the
dongle isn't usable anymore.
- If it works after e.g. waiting 4s everyone is still happy but if it
just breaks after only waiting 2s nothing is gained.
- Having to wait some
18 matches
Mail list logo
