Date: Fri, 21 Apr 2000 10:10:13 +0930 (CST) From: "Daniel O'Connor" <darius@dons.net.au> To: Brian Fundakowski Feldman <green@FreeBSD.org> Cc: Mike Pritchard <mpp@mppsystems.com>, Warner Losh <imp@village.org>, Anatoly Vorobey <mellon@pobox.com>, hackers@FreeBSD.org, "Daniel O'Connor" <doconnor@gsoft.com.au> Subject: Re: PC Keyboard Scancodes Message-ID: <XFMail.000421101013.darius@dons.net.au> In-Reply-To: <Pine.BSF.4.21.0004201650030.20816-100000@green.dyndns.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 20-Apr-00 Brian Fundakowski Feldman wrote: > Sure: Gracias. > With the new output format, I can tell that the released scancode is the > pressed scancode + 128 (| 0x80). Cool :) Yes, the kbd driver handles this automatically. >> I've altered atkbd.c to grok the new keys, I also added 'power' and 'halt' >> to kbdcontrol/syscons - so now the power button works 8-) > Heh, cool :) This goes well with my small diffs to make the ATX power > button a true 'panic', don't you think? Damn straight :) > Yeah, but along with stuff like this (usbd et al), we should have something > in the kernel (thread?) to do most of it. A unified event daemon would > probably be half in the kernel and half out of it, and it would provide a > pretty clean interface for this kind of thing (when it's not vaporware). Hmm OK.. I was thinking about something like apmd (and usbd) which spends most of its time blocked waiting for events, but a unified daemon would be nice :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.000421101013.darius>