HID stuff.

[Zephaniah E\. H. <wa...@ba...>]

Three things, but all at once because it is all on my plate right now.

First off, I am wondering if I could input.h explicitly noted with a
BSDish license so I can include it almost entirely (with some symbol
name changes to not conflict with other things) in X, possibly other
things in time as well.
(The question of it being an issue considering it is just some #defines
and some structure defs is questionable, however I prefer to play it
safe.)

Secondly, my HID quirk patch for my mouse (again), if there are problems
with it let me know?  It is attached.

Third is a bigger problem, and the more I've thought about it, the more
I've concluded that it needs to apply to both the keyboard driver, /and/
to the mice multiplexer.

There needs to be a way to say that an input device, be it a mouse or a
keyboard, or something else, has been claimed by something and should
/not/ be used for the generic code.

This becomes exceedingly obvious for the keyboard, where for X hitting
alt-F1 nicely switches you out of X because the console layer does not
know that X is using it instead of the console fd.

But as I've thought about it, I've concluded that we don't need
something specific to the keyboard (which we /might/ be able to hack
around by still setting the fd to raw mode, but that would be a really
massive hack), but that we need a generic way to say that the input
device is being handled.

I honestly don't have any ideas on how to handle it, but I'm hoping that
you might.

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

I could imagine that there might be some GPL project out there that
_deserves_ getting sued(*) and it has nothing to do with Linux.

                Linus

(*) "GNU Emacs, the defendent, did inefariously conspire to play
towers-of-hanoy, while under the guise of a harmless editor".