linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linas Vepstas <linas@austin.ibm.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Simple Newbie question
Date: Thu, 05 May 2005 18:48:47 +0000	[thread overview]
Message-ID: <20050505184847.GI11745@austin.ibm.com> (raw)
In-Reply-To: <1115181822.12538.0.camel@odyssey>

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

  parent reply	other threads:[~2005-05-05 18:48 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
2005-05-05  0:49 ` Steve Castellotti
2005-05-05 18:48 ` Linas Vepstas [this message]
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=20050505184847.GI11745@austin.ibm.com \
    --to=linas@austin.ibm.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).