linux-kernel - Re: [RFC] input: Wacom tablet driver for simple X hotplugging

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200607230124.56094.dtor@insightbb.com>
Date:	Sun, 23 Jul 2006 01:24:55 -0400
From:	Dmitry Torokhov <dtor@...ightbb.com>
To:	Magnus Vigerlöf <wigge@...foot.com>
Cc:	linux-input@...ey.karlin.mff.cuni.cz, linux-kernel@...r.kernel.org
Subject: Re: [RFC] input: Wacom tablet driver for simple X hotplugging

On Saturday 22 July 2006 06:00, Magnus Vigerlöf wrote:
> On Saturday 22 July 2006 04:09, Dmitry Torokhov wrote:
> >
> > I do not think that creating device-specific "drivers" is a good idea
> > even short term, especially in kernel. If you want a "persistent"
> > device just create a userspace daemon and listen for hotplug events.
> > When you see the input device you interested in grab it and pipe all
> > data into somewhere. Next time you see hotplug event for the same
> > device release the old instance and grab the new one. In cases when
> > final recepient of events uses ioctls to query input devices capabilities
> > you can create uinput feed back into kernel. This way your program will
> > work for all types of input devices and no kernel changes are needed.
> 
> Creating userspace device drivers is something new for me. If you have some 
> pointers to information about it I would be grateful (I've found the FUSD 
> framework through google). From what I can read from the doc of FUSD, I'll 
> have to open the inputX device if I want events from the tablet to propagate, 
> and I'm afraid I might hit the oops in evdev I described in my previous 
> thread if I do that.
> 

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.

> So.. Are the locking issues in evdev something that is about to be fixed soon 
> or should I contribute? Or do you think the issue will be completely 
> irrelevant for a user-space driver?
> 

No, I think you will still have the same issues with locking, unfortunately
I can't commint on a specific date when they will be resolved. Patches are
always welcome of course.

-- 
Dmitry
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/