On Wed, 21 Mar 2001, Greg KH wrote:
>
> 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?
After the driver has printed
'visor.c: Handspring Visor: port 1, is for Generic use and is bound to ttyUSB0'
do you consider the Handspring to be electronically attached?
If so, then why would opening /dev/ttyUSB0 return ENODEV? The open man page
says:
ENODEV pathname refers to a device special file and no
corresponding device exists. (This is a Linux
kernel bug - in this situation ENXIO must be
returned.)
I'm not sure what the ENXIO comment is about, but if the device does "exist"
it seems ENODEV should not be returned.
>From a user's point of view, having to press the hotsync button and then run
pilot-xfer (etc) within a split second is irritating and easy to miss. I would
be much happier if the open would block (much like opening a busy /dev/dsp
blocks) until the device comes online or the call is cancelled.
-Hollis
_______________________________________________
Pilot-unix mailing list
[EMAIL PROTECTED]
http://hcirisc.cs.binghamton.edu/mailman/listinfo/pilot-unix
