Re: Visor interface info [Was: Dumb terminal connection with Visor]
- From: Greg KH <greg kroah com>
- To: Richard Zach <zach math berkeley edu>
- Cc: usbvisor-unix lists sourceforge net,gnome-pilot <gnome-pilot-list gnome org>
- Subject: Re: Visor interface info [Was: Dumb terminal connection with Visor]
- Date: Fri, 11 Aug 2000 08:54:13 -0700
On Fri, Aug 11, 2000 at 02:02:30AM -0700, Richard Zach wrote:
> >
> > Maybe I should create a /proc/drivers/visor directory that gives out stats
> > on the visor(s) attached to the box. Would that be useful?
>
> I imagine that might be a good place to do that. What about the USB
> config scripts? Suppose I wanted to start a gpilotd on the hotsync
> port, and/or a pppd on the generic port every time a visor gets pugged
> in. I would probably do that with a config script in /etc/usb/config/
> as described in http://www.linux-usb.org/policy.html, right? How do I
> set it up so that this script gets called every time the visor port
> becomes active?
Yes, I think you can use the usb policy script to do that, but I haven't
had the time to look into them in depth yet.
But with devfs you can do that right now. Someone posted to the
usbvisor-devel list a few months ago with a script that is kicked off
anytime the visor is seen, using devfs. Search the archives for it if
you're interested.
Has anyone tested the usb policy scripts with the Visor driver yet?
thanks,
greg k-h
--
greg@(kroah|wirex).com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]