That is good news. I was getting suspicious when we failed in the 27th call to triplet
One thing I didn't include was the test of SM_BUS capabilities. All that would do, if failed,
is formally tell us that the i2c adapter isn't documented to support the needed calls.
Do you know what i2c chip is
Hi Christian;
Thanks for the response!
I can tell you’ve been working on
Fuse/Owfs… ;-)
Ok. So, yes, fuse is compiled with FUSE_USE_VERSION=26, and it’s not looking
at my local copy of the header files (it’s the same version anyway).
That leaves the library
paths. I’ve be
Good news: current version operates without any problem on a x86-machine with
a self-made i2c-parallel-port-adapter (see
linux/Documentation/i2c/busses/i2c-parport). Tested with a DS2482-100 and a
DS2890 digital potentiometer. Reading from and writing to this 1-wire device
works fine. Even two
ls –l /tmp/1wire/alarm
segfaults when listing alarm directory.
Haven’t found any fix for it yet..
/Christian
There is one strange behaviour in owserver…. owserver
doesn’t allow 2 remote servers.
It works if owfs has 2 remote servers defined.
This works:
/opt/owfs/bin/owserver -u -p 3008
/opt/owfs/bin/owserver -p 3005 -s 3008
/opt/owfs/bin/owfs -s 3005 –s 192.168.3.1:3000 /var/1wire/
