linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Simple Newbie question
Date: Wed, 04 May 2005 05:16:01 +0000	[thread overview]
Message-ID: <20050504051601.GA16768@kroah.com> (raw)
In-Reply-To: <1115181822.12538.0.camel@odyssey>

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

  reply	other threads:[~2005-05-04  5:16 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-04  4:43 Simple Newbie question Steve Castellotti
2005-05-04  5:16 ` Greg KH [this message]
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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050504051601.GA16768@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).