I noticed there were a missing usb_release_interface() before trying
to reconnect. That was probably why it didn't work as you wanted.
It could never claim the interface without this missing call.
BTW: Do you mind if I add a semi-colon to all lock function-calls like
STATLOCK, STATUNLOCK etc.
I think most of us have seen the occasional failures from these EMC effects, but
without your setup and observations it would be hard to hunt down. Again, thank
you.
Paul
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Jan
Kandziora
Sent: Monday, June 27,
I was wondering about that. I've been making changes and sending a tar-ball of
the source to Jan for testing.
The semicolon sounds like a good idea. My indents are also screwed up.
Paul
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of
Christian Magnusson
Nice changes, Christian.
I'm a little worried about burning CPU cycles if the adapter is unplugged. We
will aggressively try to reconnect.
I notice you make 3 attempts at reconnecting each time. That will be multiplied
by the 3 attempts ar read/write.
Would there be any harm in a delay before
Hello from Gregg C Levine
Paul here's a bit of a nasty poser for you. I remember when the OWFS
list was just cranking up, and we were discussing the porting to the
LinkSys wireless router of the OWFS binaries, this came up; a
decidedly frustrated and rather angry poster complained to use that he
Hi Gregg,
Do you want to look up the fellow? The OWFS list is searchable on
GMANE (http://dir.gmane.org/gmane.comp.file-systems.owfs.devel) and
Mail Archive
(http://www.mail-archive.com/owfs-developers%40lists.sourceforge.net/)\
I'm sure we could get OWFS to run on the NSLU2,
I agree... 3 attempts are perhaps not necessary. If it fails it should
only be necessary to try 1 attempt and then return read-error, since
it's not possible to retry the old on-going operation anyway.
I tried to start owserver to /dev/ttyS0 and then launch minicom on
/dev/ttyS0 too. This will
