[NCLUG] USB Support Recap

[jdewitt at mail.frii.com]

I've been working on a similar problem - syncing a
kodak 3500 via a usb cradle with a sync button.

The hotplug package provides a mechanism for starting
a script when a new usb device appears on the bus.
It is standard in Redhat 7.x (krud?).

This page is a good start:
http://jphoto.sourceforge.net/?selected=sync

In short, you add an entry to /etc/hotplug/usb.usermap
which describes the device in some crazy usb language,
and gives a script name. The script should be in /etc/hotplug/usb.

I'm not sure how to get the complete set of codes for a 
usb device for usb.usermap, but the system seems to recognize 
this camera with just the vendor id and the rest of the digits 
set to zero YMMV.  You might look in /proc/bus/usb/devices while
the device is plugged in and trying to sync.

Now, my current problem is that the system runs my script when I
press the sync button about four times.  This is bad. Does anyone 
know if a simple lock file check in the script is sufficient and 
the right thing to do?

Thanks,
JD


> > with it yet.  Then we'll go after the USB-cradled Visor and see if it'll
> talk
> > to KPilot.
> 
> Major problem with the USB cradled Visor -- the way it's set up, it only
> 'attaches' when you hit HotSync on the visor end, and Kpilot doesn't like
> talking like that.  At the time I was working with it, the only
> 'workarounds' were to either buy a straight serial cradle, or have fast
> enough fingers to start the sync on the computer side right after syncing on
> the visor.
> 
> --mec
> 
> _______________________________________________
> NCLUG mailing list       NCLUG at nclug.org
> 
> To unsubscribe, subscribe, or modify your settings, go to:
> http://www.nclug.org/mailman/listinfo/nclug
>