All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Hards <bhards@bigpond.net.au>
To: linux-hotplug@vger.kernel.org
Subject: Re: New mousedev device!
Date: Thu, 04 Jul 2002 21:25:34 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-102581823414408@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-102579147723532@msgid-missing>

On Fri, 5 Jul 2002 00:03, Freeze wrote:
> Hi,
>    I have a new device that could work with th input/mousedev driver. It is
> a thrust graic tablet. But it's recognized as a relative mouse, but I'd
> like to told the mousedev that it is an absolute device.
/dev/input/mouseX and /dev/input/mice are inherently relative. The code that 
you provided basically shows that mousedev.o only tries to associate with 
input devices that have relative axes, and devices that have absolute X and Y 
axes - ie mice and touchpads. The output is always relative.

Two options:
1. Use the event output driver, and manage the absolute output in userspace 
(eg using a X driver attached to /dev/input/eventX). There is some code in 
the Linuxconsole CVS, I think.
2. Use the touchpad output driver (only in linuxconsole CVS). Seen it, not 
looked in detail or used it.

Brad

-- 
http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Caffeinated soap. No kidding.
http://thinkgeek.com/sf
_______________________________________________
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:[~2002-07-04 21:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-04 14:03 New mousedev device! Freeze
2002-07-04 21:25 ` Brad Hards [this message]

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=marc-linux-hotplug-102581823414408@msgid-missing \
    --to=bhards@bigpond.net.au \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.