On Wed, Jul 30, 2008 at 3:55 AM, Paul Alfille <[EMAIL PROTECTED]> wrote:
>
> s/non-blocking/blocking/ ??
Sorry, yes. The open() is now blocking (removed O_NONBLOCK) and the
system is happy so far.
>
> Should we still put a timeout on the writes? Especially if it's blocking?
If open is changed to
What does reading 85C precisely mean? I have some DS1820 devices, powered,
on a bus and they all work but sometimes go off into this 85C mode. I know
that this is some kind of error condition but precisely what error
condition? Is there some way to use owfs to reset everything to recover
from th
On Wed, Jul 30, 2008 at 3:53 AM, Charles Spirakis <[EMAIL PROTECTED]> wrote:
> Paul --
>
> I recompiled owfs removing the EWOULDBLOCK workaround and modified
> ow_com.c to make the open non-blocking. So far things appear to be
>
s/non-blocking/blocking/ ??
working which says either solution work
Paul --
I recompiled owfs removing the EWOULDBLOCK workaround and modified
ow_com.c to make the open non-blocking. So far things appear to be
working which says either solution works for the ubuntu 7.10
environment.
I don't know the history of the code to know why non-blocking was
chosen original
