Re: Problem with reading nonblocking /dev/com in 1.7.10 and up

2012-04-13 Thread Christopher Faylor
Ping? On Tue, Apr 10, 2012 at 03:35:03PM -0400, Christopher Faylor wrote: >On Wed, Apr 11, 2012 at 01:17:05AM +0700, Abdul Muis wrote: >>I have notice that I could not read serial device (/dev/com4 or >>/dev/ttyS3) with non blocking mode since 1.7.10 and up. > >Out of curiosity, is it broken in th

Re: Problem with reading nonblocking /dev/com in 1.7.10 and up

2012-04-10 Thread Christopher Faylor
On Wed, Apr 11, 2012 at 01:17:05AM +0700, Abdul Muis wrote: >I have notice that I could not read serial device (/dev/com4 or >/dev/ttyS3) with non blocking mode since 1.7.10 and up. Out of curiosity, is it broken in the 2011-10-22 snapshot? Be careful if you install it since there may be added st

Re: Problem with reading nonblocking /dev/com in 1.7.10 and up

2012-04-10 Thread Peter Rosin
On 2012-04-10 20:17, Abdul Muis wrote: > I have notice that I could not read serial device (/dev/com4 or > /dev/ttyS3) with non blocking mode since 1.7.10 and up. I used to read > serial data while doing openGL visualization. In which, the openGL > display was not changed due to blocking mode readi

Problem with reading nonblocking /dev/com in 1.7.10 and up

2012-04-10 Thread Abdul Muis
I have notice that I could not read serial device (/dev/com4 or /dev/ttyS3) with non blocking mode since 1.7.10 and up. I used to read serial data while doing openGL visualization. In which, the openGL display was not changed due to blocking mode reading. The command is fcntl(fd, F_SETFL, FNDELAY