Path: inn.qnx.com!nntp.qnx.com!not-for-mail From: pete[a]qnx.com Newsgroups: qdn.public.qnxrtp.applications Subject: Re: xfree86 and inputtrap Date: 16 Oct 2000 17:52:09 GMT Organization: QNX Software Systems Ltd. Lines: 31 Message-ID: <8sff89$d4s$2@nntp.qnx.com> References: NNTP-Posting-Host: 209.226.137.120 X-Trace: nntp.qnx.com 971718729 13468 209.226.137.120 (16 Oct 2000 17:52:09 GMT) X-Complaints-To: usenet[a]qnx.com NNTP-Posting-Date: 16 Oct 2000 17:52:09 GMT User-Agent: tin/1.4.3-20000502 ("Marian") (UNIX) (QNX/6.00 (x86pc)) Frank Liu wrote: > It seems RTP's inputtrap is tightly linked with Photon. Can > you make it de-coupled, like QNX4's inputtrap? We will be redesigning the way input devices (console and mouse) work so that the code that talks to the raw devices stands alone. The practical consequence of this is that devc-con will not have any code in it at all to talk to the 8042 PS/2 controller, and neither will the Photon input driver. There will be something like a devc-8042 device that will create a /dev/kbd and a /dev/aux if there is a mouse attached. The upcoming USB stack will also create similar devices if you have USB keyboard/mice attached. Serial mice are already handled by /dev/ser devc-con will be changed to talk to the /dev/kbd device, which should also allow us to support international keyboards right from login You suggest that inputtrap is coupled to photon, and that is not the case. It's input itself that is coupled to Photon. devi-hirun will probably go away and be replaced with something like a devi-photon so that at least you _know_ it is coupled to Photon. Any kind of xfree86 solution would have to be done by an interested outside party, but the pieces needed to do so will be there. The redesign I'm talking about is just starting now, and will probably not be available until early next year.