linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Zephaniah E. Hull" <warp@aehallh.com>
To: "Magnus Vigerlöf" <wigge@bigfoot.com>
Cc: Dmitry Torokhov <dtor@insightbb.com>,
	linux-input@atrey.karlin.mff.cuni.cz,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] input: Wacom tablet driver for simple X hotplugging
Date: Tue, 25 Jul 2006 14:00:12 -0400	[thread overview]
Message-ID: <20060725180012.GA6399@aehallh.com> (raw)
In-Reply-To: <200607241828.32356.wigge@bigfoot.com>

[-- Attachment #1: Type: text/plain, Size: 1831 bytes --]

On Mon, Jul 24, 2006 at 06:28:32PM +0200, Magnus Vigerlöf wrote:
> On Sunday 23 July 2006 07:24, Dmitry Torokhov wrote:
> [...]
> > No, I was not talking about FUSD, just uinput driver that is in kernel
> > proper. Take a look at this:
> >
> > 	http://svn.navi.cx/misc/trunk/inputpipe/
> >
> > It allows making input devices "network-transparent" and for example
> > use joystick physically connected to one box to play game on another.
> > Hmm, actually it is almost what you need, you just need modify server
> > to multiplex events into single device instead of creating separate
> > input devices.
> 
> Interesting.. This might be handy for other projects. However, implementing 
> the same module again, but in userspace, for something that really should be 
> handled in the X-server (and will in time), nah.. I think I'll see what the 
> X-guys are up to and see how long they've come instead. Maybe I can contribute 
> there in some way.

You get basic hotplug of input devices using xf86-input-evdev with
current versions, though you'd need current git for reasonable quality
tablet support.  That may still lack some of the wacom specific bits.
(I'd have to look to see what the wacom driver does that
xf86-input-evdev doesn't do.)

Hotplug with arbitrary drivers is a harder job, and I'm still not sure
if we're talking having that done in 7.2 or 7.3.  But it is coming.

All of that said, I'm going to have to agree with others, don't do it in
the kernel, because the need to do it in the kernel is going away.

Zephaniah E. Hull.

-- 
	  1024D/E65A7801 Zephaniah E. Hull <warp@aehallh.com>
	   92ED 94E4 B1E6 3624 226D  5727 4453 008B E65A 7801
	    CCs of replies from mailing lists are requested.

A little knowledge is a dangerous thing.
So is a lot.
  -- Albert Einstein.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-07-25 18:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-21 21:13 [RFC] input: Wacom tablet driver for simple X hotplugging Magnus  Vigerlöf
2006-07-22  2:09 ` Dmitry Torokhov
2006-07-22 10:00   ` Magnus Vigerlöf
2006-07-23  5:24     ` Dmitry Torokhov
2006-07-24 16:28       ` Magnus Vigerlöf
2006-07-25 18:00         ` Zephaniah E. Hull [this message]
2006-07-24 15:11   ` Daniel Stone
2006-07-24 15:22     ` Dmitry Torokhov
2006-07-24 15:23     ` Odd values in /proc Damien Pacaud
2006-07-25 19:56       ` Jan Engelhardt
2006-07-25 19:06 ` [RFC] input: Wacom tablet driver for simple X hotplugging Andrew Morton
2006-07-29 23:45   ` Magnus Vigerlöf

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=20060725180012.GA6399@aehallh.com \
    --to=warp@aehallh.com \
    --cc=dtor@insightbb.com \
    --cc=linux-input@atrey.karlin.mff.cuni.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=wigge@bigfoot.com \
    /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).