Hi!
Can somebody give me a hint, how I get owfs to work ...
I have a Dallas DS2438Z Chip on an Elco USB Adapter.
My OS is Suse Linux 10 (Kernel 2.6.13-15.8) and I compiled
libusb 0.1.10a-4 to get Owfs (CVS) compiling.
The compilation runs successfully but after I enter
/opt/owfs/bin/./owfs -u
Seem to be a bug in module/owfs/src/c/owfs.c
#ifndef OW_MT
Fuse_add(-s , fuse_options) ; // single threaded
#endif /* OW_MT */
#if FUSE_VERSION = 26 // requires extra parameter
c = fuse_main(fuse_options.argc, fuse_options.argv, owfs_oper) ;
//printf(fuse_main=%d\n,c);
#else
Don't know yet. I was going to test it against a 9097U to see if it's a USB thing.
Also (if unrelated) I'm going to change the directory cache handling --
/uncached doesn't seem to renew the cache, and there are potential race
conditions currenty. The new design will be one large blob for the
That's embarassing. I go through and remove all the debugging printf statements when making a a release.
Fuse 2.6 uses 4 arguments:
/*
* Main function of FUSE.
*
* This is for the lazy. This is all that has to be called from the
* main() function.
*
* This function does the following:
* - parses
2.6.0-pre2
I guess it was changed back.
Thanks.
PaulOn 5/5/06, Christian Magnusson [EMAIL PROTECTED] wrote:
Strange I have downloaded 2.6.0-pre2 and there I find,/*int fuse_main(int argc, char *argv[], const struct fuse_operations *op);*/#define fuse_main(argc, argv, op)
Paul Alfille wrote:
Yes!
The ECLO isn't truly a usb adapter, at least it doesn't use the DS2490
internally.
The ELCO is a serial chip with a USB-serial adapter. So you invoke
it with
owfs /dev/ttyS0 /mnt
Again, take a look at the website. The dmesg excerpt you list doesn't
show the ECLO
Ok, I think (?!?) I am a step further ...
after following the kernel patch instructions I get:
May 5 14:21:00 nbnschochreiter kernel: usb 2-1: new full speed USB
device using uhci_hcd and address 3
May 5 14:21:00 nbnschochreiter kernel: ftdi_sio 2-1:1.0: FTDI USB
Serial Device converter
Hello!
Martin, I'm reasonably familiar with the FTDI based solutions. Check
your logs. It seems the device is being attached to USB1, not USB0.
As for why this isn't working, it just might be a bug in the libraries
associated with the device. Fuse and OWFS may just be contributing to
the issues.
[EMAIL PROTECTED]:/# owfs -u /tmp/1wire/ --error-level 3 --foreground
CONNECT: fuse mount point: /tmp/1wire/
CALL: PARSENAME path=[]
CONNECT: Adapter found: 002/006
DEFAULT: Opened USB DS9490 adapter at 002/006.
DEFAULT: Error setting up USB DS9490 adapter at 002/006.
unique: 1, opcode: INIT
Looks successful from that output. Can you see any data?
PaulOn 5/5/06, Kurt André Selbach [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED]:/# owfs -u /tmp/1wire/ --error-level 3 --foregroundCONNECT: fuse mount point: /tmp/1wire/ CALL: PARSENAME path=[]CONNECT: Adapter found: 002/006DEFAULT: Opened USB
I spoke too soon. Can you try a higher number for error_level, like 9?
There are plenty of dignostic messages in the usb setup.
PaulOn 5/5/06, Paul Alfille [EMAIL PROTECTED] wrote:
Looks successful from that output. Can you see any data?
PaulOn 5/5/06, Kurt André Selbach
[EMAIL PROTECTED]
Hi!
Thanks for the quick reply, think the problem is the ehci stuff on the asus.
tried with uhci - seems it is working now - i'll get back to you in some hours.
I will also try with error level 9 and give you some feedback - usb1.1
is too slow when usb2 i s available :P
-kurt
On 5/6/06, Paul
12 matches
Mail list logo
