linux-kernel - Re: Where to put mouse drivers?

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] [day] [month] [year] [list]

Message-ID: <4811BF53.6010408@s5r6.in-berlin.de>
Date:	Fri, 25 Apr 2008 13:24:03 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Nico Schottelius 
	<nico-lkml-where-to-put-mouse-drivers@...ottelius.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Where to put mouse drivers?

Nico Schottelius wrote:
> I am currently wondering, how and where to continue with gpm2.
...
> http://nico.schottelius.org/notizbuch-blog/archive/2008/04/24/where-to-put-mouse-drivers

>From this page:
: So the idea with gpm2 was to make it run on all the standard FOSS
: operating systems (this includes Linux, FreeBSD, NetBSD and OpenBSD
: for me) and implement the mouse de/encoding part cleanly into it.
:
: Now I met the guys from the ggi-team, which aim to use the
: os-mous-support (like wscons or /dev/input/mice).
:
: The problem I see with that approach is that each OS reimplements
: the same stuff again and again. Which is exactly what I do not like.
:
: In my opinion the OS should offer direct access to the hardware
: ports of the mice (like serial devices and ps2 devices) and do the
: de/encoding stuff in userland, which would be portable then.

So you looked at GGI already.  And how about X11, e.g. x.org?  Or SDL?

Of course these projects also have to handle other input devices besides
pointing devices (keyboards, notably) and graphics output, maybe also
sound output.  Their approaches towards pointing devices are influenced
by how the other input and output interfaces are conceived.  And they do
use a variety of backends with widely differing degrees of hardware
abstraction (e.g. run on top of X11 or on top of VNC, instead of kernel
interfaces).

You on the other hand only deal with pointing device input and console
output, so you will probably come to different conclusions.
-- 
Stefan Richter
-=====-==--- -=-- ==--=
http://arcgraph.de/sr/
--
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/