From mboxrd@z Thu Jan  1 00:00:00 1970
From: Steve Castellotti <sc@eyemagnet.net>
Date: Fri, 06 May 2005 11:52:22 +0000
Subject: Re: Simple Newbie question
Message-Id: <1115380342.3100.42.camel@odyssey>
List-Id: <linux-hotplug.vger.kernel.org>
References: <1115181822.12538.0.camel@odyssey>
In-Reply-To: <1115181822.12538.0.camel@odyssey>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: linux-hotplug@vger.kernel.org

    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