> -Original Message-
> From: Benoît Minisini [mailto:gam...@users.sourceforge.net]
>
> Can you try the unmodified SerialPort example with revision #5029?
>
> Now I do the polling with a fixed frequency. That frequency is defined
> with a new optional argument to the Open() method. It is 5
Le 11/08/2012 16:40, Benoît Minisini a écrit :
> Le 11/08/2012 15:58, Christer Johansson a écrit :
>>
>>
>>> -Original Message-
>>> From: Benoît Minisini [mailto:gam...@users.sourceforge.net]
>>>
>>> 2) By commenting all SPort1_xxxChange event handlers in the example
>>> source code?
>>
>>
Le 11/08/2012 15:58, Christer Johansson a écrit :
>
>
>> -Original Message-
>> From: Benoît Minisini [mailto:gam...@users.sourceforge.net]
>>
>> 2) By commenting all SPort1_xxxChange event handlers in the example
>> source code?
>
> Bingo! This improved things alot...
>
> Running a quick te
> -Original Message-
> From: Benoît Minisini [mailto:gam...@users.sourceforge.net]
>
> 2) By commenting all SPort1_xxxChange event handlers in the example
> source code?
Bingo! This improved things alot...
Running a quick test CPU usage was 0.0% after opening /dev/ttyAMA0 as
expected.
W
> -Original Message-
> From: Benoît Minisini [mailto:gam...@users.sourceforge.net]
>
> Can you try:
>
> 1) By using gb.qt4 instead of gb.gtk?
>
> 2) By commenting all SPort1_xxxChange event handlers in the example
> source code?
I will try later today but since the same problem exists in
Le 11/08/2012 15:12, Christer Johansson a écrit :
>
>
>> From: Benoît Minisini [mailto:gam...@users.sourceforge.net]
>>
>> As the SerialPort example asks for DTR, RNG, ... Change events, the
>> gb.net component watches if serial port file device is ready for writing
>> and uses that to watch the se
> From: Benoît Minisini [mailto:gam...@users.sourceforge.net]
>
> To confirm that, can you use gdb to run the exemple, hit
> CTRL+C during the high CPU usage, and show me what the backtrace is then?
Sorry I forgott to include system info, test was done in 3.1.1 but also
happend in 3.2.1.
[Syste
Le 11/08/2012 12:26, Christer Johansson a écrit :
> Noticed a very high CPU usage when using the serialport on a
> Raspberry Pi running Debian Squeeze and trying to understand
> whats causing it...
>
> Just opening the serialport in the SerialPort demo takes 12-26%
> depending on if using the built
