![](https://seccdn.libravatar.org/avatar/7891b1b1a5767f4b9ac1cc0723cebdac.jpg?s=120&d=mm&r=g)
Roger Oberholtzer wrote:
On Wed, 2008-08-27 at 16:17 +0200, Per Jessen wrote:
Roger Oberholtzer wrote:
I would love to know how. The serial settigns (baud rate and all) can, I think, be determined. But blocking mode is a generic file descriptor setting that I do not think is reported in /proc.
You can get/set it with fcntl().
As I do. But I would like to see it in /proc as well so I can check it at will.
Ah, I see.
I think I would take a look at how ntp does it - ntp has interface code for GPS receivers too, maybe they've worked out the right way to do it?
Been there. Their code only reads from the serial port when appropriate. Whenever it wants to sync times. Otherwise, the serial port is not accessed and data is dropped. As such, and serial port oddity like this would go un-noticed. ntp is seldom in a read state. I, however, read all the time as I need all data all the time.
That seems to be the main difference - my temp controller also only reads once I've issued the command. How about code from one of those utilities that convert serial to TCP? I can't remember any name right now, but such a utility would also have to read all the time. /Per Jessen, Zürich -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org