* Re: Simple Newbie question
2005-05-04 4:43 Simple Newbie question Steve Castellotti
@ 2005-05-04 5:16 ` Greg KH
2005-05-05 0:49 ` Steve Castellotti
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Greg KH @ 2005-05-04 5:16 UTC (permalink / raw)
To: linux-hotplug
On Wed, May 04, 2005 at 04:43:42PM +1200, Steve Castellotti wrote:
> hey all-
>
> I recently came across a USB touchscreen I'm trying to get to work
> under linux. If I plug it in under windows it registers as an HID-
> compliant device, and starts working with no additional drivers, so I
> don't believe this should be very difficult. (I'm running Fedora Core 3
> with linux kernel2.6.10-1.770_14.rhfc3.at incidentally)
>
>
> By diffing changes to /proc/bus/usb/devices, I've gotten a the info:
>
> P: Vendor\000 ProdIDÿff Rev= 1.00
>
> which I've confirmed is the correct device.
>
>
>
> I've then edited /etc/hotplug/usb.usermap and added the following lines:
>
> usbhid 0x0000 0x0000 0xffff 0x0000 0x0000
> 0x00 0x00 0x00 0x00 0x00
> 0x00 0x00000000
> keybdev 0x0000 0x0000 0xffff 0x0000 0x0000
> 0x00 0x00 0x00 0x00 0x00
> 0x00 0x00000000
> mousedev 0x0000 0x0000 0xffff 0x0000 0x0000
> 0x00 0x00 0x00 0x00 0x00
> 0x00 0x00000000
>
>
> (The device appears three times in /var/log/messages, as a "USB HID
> v1.00 Mouse" a "USB HID v1.00 Device" and a "USB HID v1.00 Keyboard" but
> of course I'm only interested in the mouse functionality)
>
>
> Diffing the changes to /sys/bus/usb/drivers/usbhid, the device is
> appearing on 2-1, so I've created a rules file in /etc/udev/rules.d:
>
> BUS="usb", PLACE="2-1", NAME="input/mouse0"
>
>
>
> The device seems to be recognized as a usbhid device even without
> the hotplug or udev changes, but gpm fails to recognize it. Even after
> the changes, while /dev/input/mouse0 will appear correctly, gpm still
> will not recognize the mouse.
You should not need any hotplug or udev changes.
But you should point gpm to use the new /dev/input/mouse0 or the
/dev/input/mice device node. Good luck with that.
greg k-h
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Simple Newbie question
2005-05-04 4:43 Simple Newbie question Steve Castellotti
2005-05-04 5:16 ` Greg KH
@ 2005-05-05 0:49 ` Steve Castellotti
2005-05-05 18:48 ` Linas Vepstas
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: Steve Castellotti @ 2005-05-05 0:49 UTC (permalink / raw)
To: linux-hotplug
Thanks .. but the device doesn't create the /dev/input/mouse0 (or
any other device entry) unless I manually create that udev rule file.
That being said, when I do use the udev rule file, stopping the gpm
daemon via init.d script and than calling gpm via:
# gpm -m /dev/input/mouse0 -t ps2
doesn't seem have any effect. I've tried with /dev/input/mice and
with types "imps2" "pnp" and "ms" as well to no effect.
Might I have to somehow modify the usb mouse driver module to recognize
this device? Is there a table that I simply need to make an entry into?
Again, thanks
Steve Castellotti
On Tue, 2005-05-03 at 22:16 -0700, Greg KH wrote:
> > The device seems to be recognized as a usbhid device even without
> > the hotplug or udev changes, but gpm fails to recognize it. Even after
> > the changes, while /dev/input/mouse0 will appear correctly, gpm still
> > will not recognize the mouse.
>
> You should not need any hotplug or udev changes.
>
> But you should point gpm to use the new /dev/input/mouse0 or the
> /dev/input/mice device node. Good luck with that.
>
> greg k-h
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.
> Get your fingers limbered up and give it your best shot. 4 great events, 4
> opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
> win an NEC 61 plasma display. Visit http://www.necitguy.com/?r
> _______________________________________________
> Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
> Linux-hotplug-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
Steve Castellotti
Technical Director
Eye Magnet - New Zealand
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Simple Newbie question
2005-05-04 4:43 Simple Newbie question Steve Castellotti
2005-05-04 5:16 ` Greg KH
2005-05-05 0:49 ` Steve Castellotti
@ 2005-05-05 18:48 ` Linas Vepstas
2005-05-06 11:50 ` Steve Castellotti
2005-05-06 11:52 ` Steve Castellotti
4 siblings, 0 replies; 6+ messages in thread
From: Linas Vepstas @ 2005-05-05 18:48 UTC (permalink / raw)
To: linux-hotplug
On Thu, May 05, 2005 at 12:49:12PM +1200, Steve Castellotti was heard to remark:
>
> Thanks .. but the device doesn't create the /dev/input/mouse0 (or
> any other device entry) unless I manually create that udev rule file.
> That being said, when I do use the udev rule file, stopping the gpm
> daemon via init.d script and than calling gpm via:
>
> # gpm -m /dev/input/mouse0 -t ps2
>
> doesn't seem have any effect. I've tried with /dev/input/mice and
> with types "imps2" "pnp" and "ms" as well to no effect.
>
>
>
> Might I have to somehow modify the usb mouse driver module to recognize
> this device? Is there a table that I simply need to make an entry into?
I think there's a way of getting gpm to report any raw input it recieves
... is it receiving any input at all?
--linas
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Simple Newbie question
2005-05-04 4:43 Simple Newbie question Steve Castellotti
` (2 preceding siblings ...)
2005-05-05 18:48 ` Linas Vepstas
@ 2005-05-06 11:50 ` Steve Castellotti
2005-05-06 11:52 ` Steve Castellotti
4 siblings, 0 replies; 6+ messages in thread
From: Steve Castellotti @ 2005-05-06 11:50 UTC (permalink / raw)
To: linux-hotplug
Well, I'm learning anyway.
If I remove all of my modifications to udev and hotplug, and just
plug the device in as normal, four devices are created when I plug in
the device:
Mouse:
/dev/input/event2
/dev/input/js0
Keyboard:
/dev/usbhid0
/dev/input/event3
Three device entries are created under /sys/bus/usb/devices, one for
the Mouse, one for "Comms" and one for "Keyboard"
Comparing to when I plug in a USB microsoft intellimouse, I get two
devices:
/dev/input/mouse0
/dev/input/event4
Now if I try:
#gpm -D -m /dev/input/event4 -Rraw (the "event" device created for
the microsoft mouse)
I get:
[root@eyemagnet hotplug]# gpm -D -m /dev/input/event4 -Rraw
*** info [startup.c(95)]: Started gpm successfully. Entered daemon mode.
*** debug [console.c(125)]: Screen size: 80 - 25
*** debug [gpm.c(159)]: x 10, y 20
...which stays like that until I move the mouse. Once I move the mouse
I endlessly get:
*** err [gpm.c(89)]: Error in read()ing first: No such file or directory
*** debug [gpm.c(533)]: selected 1 times
...to standard out.
The *identical* thing happens if I do:
# gpm -D -m /dev/input/event2 -Rraw (the "event" device created by the
touchscreen)
...with the looping error messages not appearing until I touch the
screen somewhere. So there's definitely a form of interaction going on.
It seems that Linux is creating a "/dev/input/js0" (joystick) device for
the "mouse" portion of the touchscreen, instead of
creating /dev/input/mouse0 like it knows to do with the Intellimouse.
Surely I'm getting close and its a matter of telling hotplug's
input.agent (or similar) to recognize the screen as a mouse instead of a
joystick?
Is the correct file to modify:
/lib/modules/<kernel version>/modules.inputmap
(?)
and if so is there a reference for how to determine the correct values?
Thanks heaps for all the help everyone!
Steve Castellotti
On Thu, 2005-05-05 at 13:48 -0500, Linas Vepstas wrote:
> > # gpm -m /dev/input/mouse0 -t ps2
> >
> > doesn't seem have any effect. I've tried with /dev/input/mice and
> > with types "imps2" "pnp" and "ms" as well to no effect.
> >
> >
> >
> > Might I have to somehow modify the usb mouse driver module to recognize
> > this device? Is there a table that I simply need to make an entry into?
>
> I think there's a way of getting gpm to report any raw input it recieves
> ... is it receiving any input at all?
>
> --linas
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Simple Newbie question
2005-05-04 4:43 Simple Newbie question Steve Castellotti
` (3 preceding siblings ...)
2005-05-06 11:50 ` Steve Castellotti
@ 2005-05-06 11:52 ` Steve Castellotti
4 siblings, 0 replies; 6+ messages in thread
From: Steve Castellotti @ 2005-05-06 11:52 UTC (permalink / raw)
To: linux-hotplug
Well, I'm learning anyway.
If I remove all of my modifications to udev and hotplug, and just
plug the device in as normal, four devices are created when I plug in
the device:
Mouse:
/dev/input/event2
/dev/input/js0
Keyboard:
/dev/usbhid0
/dev/input/event3
Three device entries are created under /sys/bus/usb/devices, one for
the Mouse, one for "Comms" and one for "Keyboard"
Comparing to when I plug in a USB microsoft intellimouse, I get two
devices:
/dev/input/mouse0
/dev/input/event4
Now if I try:
#gpm -D -m /dev/input/event4 -Rraw (the "event" device created for
the microsoft mouse)
I get:
[root@eyemagnet hotplug]# gpm -D -m /dev/input/event4 -Rraw
*** info [startup.c(95)]: Started gpm successfully. Entered daemon mode.
*** debug [console.c(125)]: Screen size: 80 - 25
*** debug [gpm.c(159)]: x 10, y 20
...which stays like that until I move the mouse. Once I move the mouse
I endlessly get:
*** err [gpm.c(89)]: Error in read()ing first: No such file or directory
*** debug [gpm.c(533)]: selected 1 times
...to standard out.
The *identical* thing happens if I do:
# gpm -D -m /dev/input/event2 -Rraw (the "event" device created by the
touchscreen)
...with the looping error messages not appearing until I touch the
screen somewhere. So there's definitely a form of interaction going on.
It seems that Linux is creating a "/dev/input/js0" (joystick) device for
the "mouse" portion of the touchscreen, instead of
creating /dev/input/mouse0 like it knows to do with the Intellimouse.
Surely I'm getting close and its a matter of telling hotplug's
input.agent (or similar) to recognize the screen as a mouse instead of a
joystick?
Is the correct file to modify:
/lib/modules/<kernel version>/modules.inputmap
(?)
and if so is there a reference for how to determine the correct values?
Thanks heaps for all the help everyone!
Steve Castellotti
On Thu, 2005-05-05 at 13:48 -0500, Linas Vepstas wrote:
> > # gpm -m /dev/input/mouse0 -t ps2
> >
> > doesn't seem have any effect. I've tried with /dev/input/mice and
> > with types "imps2" "pnp" and "ms" as well to no effect.
> >
> >
> >
> > Might I have to somehow modify the usb mouse driver module to recognize
> > this device? Is there a table that I simply need to make an entry into?
>
> I think there's a way of getting gpm to report any raw input it recieves
> ... is it receiving any input at all?
>
> --linas
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
^ permalink raw reply [flat|nested] 6+ messages in thread