All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <p_gortmaker@yahoo.com>
To: Andries.Brouwer@cwi.nl
Cc: linux-kernel@vger.kernel.org
Subject: Re: kbdbook.tmpl
Date: Mon, 01 Apr 2002 00:27:52 -0500	[thread overview]
Message-ID: <3CA80BF8.66DCB7E@yahoo.com> (raw)
In-Reply-To: <UTC200203312118.VAA468180.aeb@cwi.nl>

Andries.Brouwer@cwi.nl wrote:
> 
> Spent the past hour or two documenting the keyboard ioctls.

Great!

> Comments are welcome, both about the factual contents
> and about the style and layout. The idea is to eventually
> have all ioctls documented.

Minor nit, but if this is headed for Documentation/ioctl/* or similar,
maybe we can avoid having N copies of the usual GPL boiler plate; one
copy vs. one in each of kbd_ioctl, tty_ioctl, blk_ioctl, etc etc ?

>  This "cooked" mode comes in two flavours: <constant>K_XLATE</constant>,
>  which is the default, and <constant>K_UNICODE</constant> (see below).
+  See also kbd_mode(1).
^^^^^^^^^^^^^^^^^^^^^^^^

I see you haven't added info on all of the KD* ioctl entries - some of 
which I agree aren't really kbd related (e.g. KDMKTONE) - did you forsee
putting these in another file, perhaps with the other vt ioctls?

Paul.
--
main(){int m=19248;if(!fork())for(;;ioctl(0,m,(1<<23)+(rand()&2047)),ioctl
(0,m+2,rand()&7),sleep(1));}/* Hours of entertainment on Linux Console! */


  reply	other threads:[~2002-04-01  8:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-31 21:18 kbdbook.tmpl Andries.Brouwer
2002-04-01  5:27 ` Paul Gortmaker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-01  9:37 kbdbook.tmpl Andries.Brouwer

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=3CA80BF8.66DCB7E@yahoo.com \
    --to=p_gortmaker@yahoo.com \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.