Hello,
I was planning on developing an input driver for the Microtouch
"Capacitive Touch" touchscreen device. I have been using a character
based device driver that has been working out really well
(http://www.wnsa.net/grandamp). If there is interest for me to
complete, or collaborate, with this work please let me know. I have
also finally received the firmware specification for this Microtouch
(Now 3M) device. Specifically: 14-205 && 14-206 controllers. (0x0596,
0x0001). I received the documentation from 3M last week.
If there is interest in this, please let me know! Otherwise if this is
simply a duplication of effort, and this device can be covered by an
existing input driver, please let me know!
Regards,
Todd E. Johnson
[EMAIL PROTECTED]
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]] On
> Behalf Of Danny Rathjens
> Sent: Saturday, June 01, 2002 3:03 PM
> To: [EMAIL PROTECTED]
> Subject: Re: [Linux-usb-users] figuring out device numbers from /proc
>
>
> Brad Hards wrote:
> > On Sat, 1 Jun 2002 07:28, Danny Rathjens wrote:
> >
> >>Is it possible to deduce N for /dev/input/eventN by examining
> >>/proc/bus/usb/devices? IOW, does usb topology map directly to input
> >>event devices, or does it depend on the quirks of the individual usb
> >>drivers involved?
> >
> > There is no linkage. Why would there be? USB isn't the only
> thing that the
> > input layer handles (even in 2.4). USB just registers input
> devices. There
> > might not even be event support - USB doesn't care.
> >
> >
> >>If I can't figure out which event stream to use from /proc I guess
> >>I would have to modify the driver so that it reports the
> event stream
> >>it is assigned to kernel log.
> >
> > Don't. There is a standard ioctl that tells you (for a
> particular event
> > interface) what device it matches - EVIOCGBUS.
>
> Thank you. I had come to a similar conclusion, but was planning
> on using EVIOCGID or EVIOCGNAME which I found in input/evdev.c
> I see EVIOCGBUS defined in input.h but I do not see where it
> is actually
> used.
>
> I also noticed this commented line in evdev_connect() in evdev.c:
> // printk(KERN_INFO "event%d: Event device for
> input%d\n", minor,
> dev->number);
>
> I was thinking of just uncommenting it and adding dev->name and
> dev->idvendor
> to the output since I am lazy. But I guess the ioctl method would be
> the most
> proper, ;)
> >
> > If that doesn't help, perhaps you need to tell us what you
> are trying to do.
>
> I'm using a usb microtouch touchscreen for a linux-based kiosk
> (http://www.wirespring.com is our company). For the X module
> to use it we
> have to tell it which event stream to use. Up until now we had just
> hard coded the value in XF86Config but now I need to
> programatically set
> it so that it will work for different variations of
> keyboard/mouse/monitor.
>
> Thanks again.
> --
> _.,-*~`^'~*-,._ Danny Rathjens _.,-*~`^'~*-,._
> Caught a sudden glimpse;
> Accidental ecstasy:
> Frequent reminisce.
>
>
> _______________________________________________________________
>
> Don't miss the 2002 Sprint PCS Application Developer's Conference
> August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
>
> _______________________________________________
> [EMAIL PROTECTED]
> To unsubscribe, use the last form field at:
> https://lists.sourceforge.net/lists/listinfo/linux-usb-users
>
_______________________________________________________________
Don't miss the 2002 Sprint PCS Application Developer's Conference
August 25-28 in Las Vegas -- http://devcon.sprintpcs.com/adp/index.cfm
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-users
