Sure.
On Wednesday 22 June 2005 05:07 pm, Christian Magnusson wrote:
Almost done now... Everything seems to be working with offset and
direct_io option. I'll make some more tests from work tomorrow and
I'll check in the changes from there.
I'm a bit annoyed about the error functions
The problem is basically that offset wasn't supported in ow_read.c
for all types.
Two system calls where made when reading 10.061847000800/temperature.
First read return 15 bytes, and the second call was reading from
offset=15 and returned errno=-ENOTAVAIL according to the owfs source.
I have
Almost done now... Everything seems to be working with offset and
direct_io option. I'll make some more tests from work tomorrow and
I'll check in the changes from there.
I'm a bit annoyed about the error functions though...
LEVEL_CALL() will print the errno-message, and it's very common
that
BTW: Shouldn't we try to mount the fuse-directory with the
-odirect_io option just to make the read-operations atomic.
I'm mostly thinking about the the LCD's counters.ALL which reset
every time you read it, but without this option two different
processes could catch a pressed button.
cat
Absolutely. Do you want to do it, or should I?
Paul
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
Christian Magnusson
Sent: Tuesday, June 21, 2005 2:54 AM
To: owfs-developers
Subject: [Owfs-developers] direct_io in fuse
BTW: Shouldn't we try to mount
