From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] kbdputc() in devcons.c in 9front?
Date: Thu, 17 Jul 2014 12:44:38 -0400 [thread overview]
Message-ID: <50a05f8e435c96091aedcd173146709f@ladd.quanstro.net> (raw)
In-Reply-To: <97b8c27495a8ebca030bd23bbf5f47e8@felloff.net>
> kbdfs removes some code duplication like the
> latin1 composing. vncs in 9front just runs another
> instance of kbdfs to provide cons and kbd files
> instead of reimplementing the kernels console code.
i found the major source of duplication was the n copies
of (different!) scan code tables in the various /sys/src/9/*/kbd.c
these differences appear to all be accidental.
consolidating them into port/devpckb.c which provides both /dev/kbin
and /dev/kbmap, and removing or reducing $arch/kbd.c to $arch/i8042.c
got a lot of the cleanup done without breaking interfaces.
it would be nice to get away from the annoying pc scan code interface,
but the cost is going to be compatability, and that cost seems too much
to me at this point. the only way to do something like this imo would be
to agree and coordinate changes.
/dev/kbd seems reasonable if you've got that kind of problem. but
i don't see the benefit to using it where not formerly required,
but i do see a compatibility downside.
i also prefer having the keyboard in the kernel, since i do have kernels
with no user space. norio(8) was written to deal with console interrupt
for a particular project. think of it as rio with no graphics, and one
pre-defined window. but i don't think it's a very good idea. there are
better options. (like rio.)
and yes, that's like, ya know, my opinion, man. so like, whatever. :-)
- erik
next prev parent reply other threads:[~2014-07-17 16:44 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 [this message]
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
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=50a05f8e435c96091aedcd173146709f@ladd.quanstro.net \
--to=quanstro@quanstro.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).