On Wed, Feb 15, 2006 at 11:25:33AM +0100, Volker Christian wrote: > Package: hal > Version: 0.4.8-8 > Severity: important > > Connecting a Windows-CE device via USB causes a call to > hald-probe-serial. This is bad for a Windows-CE device as > hald-probe-serial is trying to open the ttyUSBx device what causes the > Windows-CE device to start the connection-initiation-sequence. This > sequence > couldn't succeed, because no program is waiting for a connection on the > pc-side. This wouldn't be that bad if the Windows-CE device would accept > a second triggering of the connection-initiation-seqnence by appropriate > desktop software (synce-serial). But unfortunately, Windows-CE devices > didn't allow a second trigger. Hence, with the present hal-package no > USB connection with an Windows-CE device is possible. > > A proper solution would be the integration of the SynCE package > (especially the synce-serial package) into hal, such that > synce-serial-start would be called instead of hald-probe-serial on > device-connect and that synce-serial-abort would be called after the > device is unplugged. > > Please let me know how we could achieve this goal - or maybe an other > appropriate solution.
Imho the correct solution for hal is not to probe USB serial ports. The only reason for the serial port prober is that you can't know if /dev/ttyS3 actually corresponds to a real device. But that's not an issue for USB. Now i must admin that i don't know a lot about how synce works, but it's my opinion that hal should remain a facts database and shouldn't start triggering system setup programs. That should be done on a higher level. What do you think ? Sjoerd -- "Protozoa are small, and bacteria are small, but viruses are smaller than the both put together." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
