On Wed, Mar 21, 2001 at 03:44:43AM -0500, Hollis R Blanchard wrote:
>
> Also, I'm very curious about USB hotsyncs. This is what I do now (thanks
> Keyspan!), and getting the timing right is quite irritating.
>
> It seems like a limitation in the kernel wrt USB serial. Can someone (Greg? :)
> elaborate more?
>
> I see the extension cord analogy at
> http://www.gnu-designs.com/pilot-link/howto/ppp/index.html#usbconfig, but I'm
> not satisfied with that.
>
> 'visor.c: Handspring Visor: port 1, is for Generic use and is bound to ttyUSB0'
> says to me that future reads and writes could at least be queued rather than
> return a "no such device" error. Are there any plans to change this behavior?
I don't understand what you mean by this. Yes, while the visor is
attached electronically through USB to the machine, the driver can talk
to the device. When it isn't it can't. How can I change this behavior?
It's not a USB serial limitation, but a function of how Handspring
chose to implement the USB hardware (and one that makes sense from a
designer's view due to battery life and other things). Windows works
with the Visor this same way, how can Linux or FreeBSD be any different?
Does this help any?
greg k-h
--
greg@(kroah|wirex).com
_______________________________________________
Pilot-unix mailing list
[EMAIL PROTECTED]
http://hcirisc.cs.binghamton.edu/mailman/listinfo/pilot-unix
