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  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]
Date:	Fri, 21 Jul 2006 22:09:04 -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

Hi Magnus,

On Friday 21 July 2006 17:13, Magnus Vigerlöf wrote:
> I'd appreciate whether you think this is a viable idea to make it as a
> generic driver instead or should I continue with the Wacom-specific
> one. I know the 'right' thing would be to make X truly hot-plug aware,
> but this driver is something that would be possible to use in current
> systems without any problems.
> 

Yes, I think fixing X would ultimately be time better spent. 

> If it is a viable idea; Which other devices/types of device do you
> think could be of interest to handle in a similar fashion? Tablets of
> different makes/models are obvious, but are there any others that
> would benefit from a similar driver?
> 

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.

-- 
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/

Powered by blists - more mailing lists