From: James Tomaschke <james@orcasystems.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Raw Input Driver
Date: Fri, 20 Mar 2009 15:23:57 -0700 [thread overview]
Message-ID: <49C4177D.5070904@orcasystems.com> (raw)
In-Reply-To: <8935727bfb98e59a33fb7a243441ed8f@terzarima.net>
Charles Forsyth wrote:
> it's not as though the underlying devices
> weren't separate streams; they are, and it makes sense for the view
> of them to reflect that. it also makes it easier to add new input
> devices. i see already you've got 'k' and 'm', with surprisingly different
> content, but what about that fingerprint thingy to unlock the cheats? or perhaps more to the point the
> 'w' for wheel and 'p' for pedals? you'll never finish.
I did have an implementation where the program could open the driver and
select which input stream they were interested in from an enumerated
list, if more than one stream is selected it will mux them (interrupt
events are simply discarded if not desired).
As far as 'k' 'm' 'w' 'p', better choice would be buttons/axis. A three
button mouse with wheel would have 5 buttons and 2 axis. This can keep
the complexity down in the driver.
next prev parent reply other threads:[~2009-03-20 22:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-20 7:00 James Tomaschke
2009-03-20 7:07 ` lucio
2009-03-20 7:57 ` James Tomaschke
2009-03-20 9:12 ` erik quanstrom
2009-03-20 11:05 ` Charles Forsyth
2009-03-20 10:54 ` Francisco J Ballesteros
2009-03-20 11:07 ` cinap_lenrek
2009-03-20 11:28 ` roger peppe
2009-03-20 11:39 ` Fco. J. Ballesteros
2009-03-20 12:04 ` erik quanstrom
2009-03-20 11:32 ` erik quanstrom
2009-03-20 12:23 ` Charles Forsyth
2009-03-20 12:16 ` erik quanstrom
2009-03-20 13:03 ` roger peppe
2009-03-20 13:37 ` tlaronde
2009-03-20 14:26 ` roger peppe
2009-03-20 15:02 ` tlaronde
2009-03-20 15:14 ` tlaronde
2009-03-20 12:52 ` maht
2009-03-20 22:23 ` James Tomaschke [this message]
2009-03-20 9:13 ` lucio
2009-03-20 14:18 Francisco J Ballesteros
2009-03-20 14:29 ` roger peppe
2009-03-20 14:22 Francisco J Ballesteros
2009-03-20 14:32 ` roger peppe
2009-03-20 15:17 ` lucio
2009-03-20 14:35 Francisco J Ballesteros
2009-03-20 14:46 Francisco J Ballesteros
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=49C4177D.5070904@orcasystems.com \
--to=james@orcasystems.com \
--cc=9fans@9fans.net \
/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).