From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <8935727bfb98e59a33fb7a243441ed8f@terzarima.net> References: <8935727bfb98e59a33fb7a243441ed8f@terzarima.net> Date: Fri, 20 Mar 2009 11:54:43 +0100 Message-ID: <8ccc8ba40903200354i1e467179k6285dca93d6469a9@mail.gmail.com> From: Francisco J Ballesteros To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] Raw Input Driver Topicbox-Message-UUID: bff52214-ead4-11e9-9d60-3106f5b1d025 There's a kbdin device used by the usb keyboard driver to feed scan codes (from usb) to the kernel keyboard driver for processing. If you are modifying kbd to read scan codes as well, this may be relevant. On Fri, Mar 20, 2009 at 12:05 PM, Charles Forsyth w= rote: > i think it is a mistake to reintroduce single even streams let alone `cal= lbacks'. > > it's easy enough to provide a device (say /dev/scancode) or a consctl mod= e > that gives you the raw keyboard codes. we used the former in inferno, > but the latter might be more logical since it's a different mode > of the same device. =C2=A0either way, it worked fine in native inferno. > (i can't remember how much was in the hosted versions, but i thought ther= e > was support for scan codes in windows and x11.) > > the ordering problem is misleading: you need timely response for > interactive applications; it's a reasonably straightforward application > of real-time programming. =C2=A0(by the way, if you're passing low-level > things like that across lossy wireless networks, you're possibly > not addressing the most relevant problem first.) =C2=A0the effects you're= trying to synchronise > are typically changes to data structures inside a program (including effe= cts on the display), > so that's where the synchronisation and interlocking should be. > > it's not as though the underlying devices > weren't separate streams; they are, and it makes sense for the view > of them to reflect that. it also makes it easier to add new input > devices. i see already you've got 'k' and 'm', with surprisingly differen= t > content, but what about that fingerprint thingy to unlock the cheats? or = perhaps more to the point the > 'w' for wheel and 'p' for pedals? you'll never finish. > > I include these for people that haven't seen them before: > > http://swtch.com/~rsc/thread/cws.pdf > http://herpolhode.com/rob/lec5.pdf > >