Armin Bauer wrote:
I was uber-conservative the first time and did a sleep(30) just before
the close of the while() loop. This obviously took a very long time
(sleep for 30 seconds after each write), but it WORKED! I've dropped it
down to 5 and am recompiling now.
This is probably much less than
Armin Bauer wrote:
This is probably much less than an ideal solution, but hopefully it'll
help those more familiar with the codebase come up with a cleaner solution.
I am not familiar with the irmc plugin, but shouldnt that be writen with
poll/select to check if it is possible to write to the soc
On Sun, 2004-08-01 at 10:39, Phil Dibowitz wrote:
> Phil Dibowitz wrote:
> > Unfortunately the DCU-11 cable that connects the phone is a USB to
> > Serial converter, and the phone acts as a basic serial device taking AT
> > commands.
> >
> > Therefore multisync writes some data, and then tries a
Phil Dibowitz wrote:
Unfortunately the DCU-11 cable that connects the phone is a USB to
Serial converter, and the phone acts as a basic serial device taking AT
commands.
Therefore multisync writes some data, and then tries a few times to
write more data but fails and therefore gives up.
I manag
Folks,
I mentioned this on the users list, but (1) I think it's more
appropriate here and (2) I didn't get any response there.
After getting a kernel patch for the pl2303 driver, I can now get
multisync to talk to my Sony Ericcson T637 over a USB cable -- but only
to a certain extent.
It sync'
