On 08/26/2016 08:43 AM, Stefan Roese wrote:
> Hi Andrew,
>
> On 26.08.2016 15:40, Andrew F. Davis wrote:
>> On 08/26/2016 12:18 AM, Stefan Roese wrote:
>>> On 25.08.2016 20:43, Andrew F. Davis wrote:
When waiting for input in CYGACC_COMM_IF_GETC_TIMEOUT we delay 2
seconds by incrementing
Hi Andrew,
On 26.08.2016 15:40, Andrew F. Davis wrote:
On 08/26/2016 12:18 AM, Stefan Roese wrote:
On 25.08.2016 20:43, Andrew F. Davis wrote:
When waiting for input in CYGACC_COMM_IF_GETC_TIMEOUT we delay 2
seconds by incrementing and checking a counter variable every 20
uSeconds. The overhea
On 08/26/2016 12:18 AM, Stefan Roese wrote:
> On 25.08.2016 20:43, Andrew F. Davis wrote:
>> When waiting for input in CYGACC_COMM_IF_GETC_TIMEOUT we delay 2
>> seconds by incrementing and checking a counter variable every 20
>> uSeconds. The overhead in the loop calling tstc() millions of times
>>
On 25.08.2016 20:43, Andrew F. Davis wrote:
When waiting for input in CYGACC_COMM_IF_GETC_TIMEOUT we delay 2
seconds by incrementing and checking a counter variable every 20
uSeconds. The overhead in the loop calling tstc() millions of times
causes the timeout to be closer to 20 seconds. Delay lo
4 matches
Mail list logo