9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: cinap_lenrek@felloff.net
To: 9fans@9fans.net
Subject: Re: [9fans] kbdputc() in devcons.c in 9front?
Date: Thu, 17 Jul 2014 20:41:06 +0200	[thread overview]
Message-ID: <57491b2937028588564c58c83826c506@felloff.net> (raw)
In-Reply-To: <2bd8d0124ea7bda9b5ba618c07633cab@ladd.quanstro.net>

rio multiplexes /dev/kbd, so it opens it and derives the windows kbd
and cons files from it. it obviously has to read /dev/kbd to multiplex
it. now, the incompatibility is that opening /dev/kbd disables /dev/cons
input.

the reason is that /dev/cons is buffered but pressing keys on the keyboard
will result in characters being queued to /dev/cons. /dev/kbd reading programs
should *not* require a dummy reader proc to flush duplicated console input in
addition to reading /dev/kbd. you open /dev/kbd and the keyboard is yours.

it is also harder to filter or translate multiple asynchronously read
file stremas instead of just one. and filtering /dev/kbd is not much
differnet from filtering /dev/cons. in addition, you have keyboard
chords.

--
cinap



  parent reply	other threads:[~2014-07-17 18:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-17  1:59 kokamoto
2014-07-17  7:39 ` cinap_lenrek
2014-07-17 16:44   ` erik quanstrom
2014-07-17  8:02 ` cinap_lenrek
2014-07-17 16:15   ` erik quanstrom
2014-07-17 17:54     ` sl
2014-07-17 18:41     ` cinap_lenrek [this message]
2014-07-17 10:45 ` Steve Simon
2014-07-17 10:58 ` Steffen Nurpmeso
2014-07-17 12:17 ` cinap_lenrek
2014-07-18  0:13   ` kokamoto
2014-07-18  0:16     ` cinap_lenrek
2014-07-19 12:56 ` kokamoto

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57491b2937028588564c58c83826c506@felloff.net \
    --to=cinap_lenrek@felloff.net \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).