A little typos and grammer fixes.
This commit is contained in:
parent
9e15a0dbb1
commit
92e0a1145f
@ -1,5 +1,5 @@
|
||||
.\"
|
||||
.\" $Id: keyboard.4,v 1.13 1998/03/12 07:30:34 charnier Exp $
|
||||
.\" $Id: keyboard.4,v 1.14 1998/06/08 06:11:59 jkoshy Exp $
|
||||
.\"
|
||||
.Dd January 8, 1995
|
||||
.Dt KEYBOARD 4 i386
|
||||
@ -15,7 +15,7 @@ To switch between the virtual consoles use the sequence
|
||||
.Ar ALT+Fn
|
||||
, which means hold down ALT and press one of the function keys. The
|
||||
virtual console with the same number as the function key is then
|
||||
selected as the current virtual console, and given exclusive use of
|
||||
selected as the current virtual console and given exclusive use of
|
||||
the keyboard and display.
|
||||
|
||||
The console allows entering values that are not physically
|
||||
@ -68,7 +68,7 @@ The field n_keys tells the system how many keydefinitions (scancodes)
|
||||
follows. Each scancode is then specified in the key_t substructure.
|
||||
|
||||
Each scancode can be translated to any of 8 different values, depending
|
||||
on the shift, control, and alt state. These eight possibilities is
|
||||
on the shift, control, and alt state. These eight possibilities are
|
||||
represented by the map array, as shown below:
|
||||
|
||||
alt
|
||||
@ -79,14 +79,14 @@ represented by the map array, as shown below:
|
||||
0x1E 'a' 'A' 0x01 0x01 'a' 'A' 0x01 0x01
|
||||
|
||||
This is the default mapping for the key labelled 'A' which normally has
|
||||
scancode 0x1E. The eight states is as shown, giving the 'A' key its
|
||||
scancode 0x1E. The eight states are as shown, giving the 'A' key its
|
||||
normal behavior.
|
||||
The spcl field is used to give the key "special" treatment, and is
|
||||
interpreted as follows.
|
||||
Each bit correspond to one of the states above. If the bit is 0 the
|
||||
Each bit corresponds to one of the states above. If the bit is 0 the
|
||||
key emits the number defined in the corresponding map[] entry.
|
||||
If the bit is 1 the key is "special". This means it does not emit
|
||||
anything, instead it changes the "state". That means it is a shift,
|
||||
anything; instead it changes the "state". That means it is a shift,
|
||||
control, alt, lock, switch-screen, function-key or no-op key.
|
||||
The bitmap is backwards ie. 7 for base, 6 for shift etc.
|
||||
|
||||
@ -94,7 +94,7 @@ The flgs field defines if the key should react on caps-lock (1),
|
||||
num-lock (2), both (3) or ignore both (0).
|
||||
|
||||
The kbdcontrol utility is used to load such a description into/outof
|
||||
the kernel at runtime. This make it possible to change the key
|
||||
the kernel at runtime. This makes it possible to change the key
|
||||
assignments at runtime, or more important to get (GIO_KEYMAP ioctl)
|
||||
the exact key meanings from the kernel (fx. used by the X server).
|
||||
|
||||
@ -113,7 +113,7 @@ The field keynum defines which function key that is programmed.
|
||||
The array keydef should contain the new string to be used (MAXFK long),
|
||||
and the length should be entered in flen.
|
||||
|
||||
The GETFKEY ioctl call works in a similar manner, execpt it returns
|
||||
The GETFKEY ioctl call works in a similar manner, except it returns
|
||||
the current setting of keynum.
|
||||
|
||||
The function keys are numbered like this:
|
||||
|
@ -1,5 +1,5 @@
|
||||
.\"
|
||||
.\" $Id: keyboard.4,v 1.13 1998/03/12 07:30:34 charnier Exp $
|
||||
.\" $Id: keyboard.4,v 1.14 1998/06/08 06:11:59 jkoshy Exp $
|
||||
.\"
|
||||
.Dd January 8, 1995
|
||||
.Dt KEYBOARD 4 i386
|
||||
@ -15,7 +15,7 @@ To switch between the virtual consoles use the sequence
|
||||
.Ar ALT+Fn
|
||||
, which means hold down ALT and press one of the function keys. The
|
||||
virtual console with the same number as the function key is then
|
||||
selected as the current virtual console, and given exclusive use of
|
||||
selected as the current virtual console and given exclusive use of
|
||||
the keyboard and display.
|
||||
|
||||
The console allows entering values that are not physically
|
||||
@ -68,7 +68,7 @@ The field n_keys tells the system how many keydefinitions (scancodes)
|
||||
follows. Each scancode is then specified in the key_t substructure.
|
||||
|
||||
Each scancode can be translated to any of 8 different values, depending
|
||||
on the shift, control, and alt state. These eight possibilities is
|
||||
on the shift, control, and alt state. These eight possibilities are
|
||||
represented by the map array, as shown below:
|
||||
|
||||
alt
|
||||
@ -79,14 +79,14 @@ represented by the map array, as shown below:
|
||||
0x1E 'a' 'A' 0x01 0x01 'a' 'A' 0x01 0x01
|
||||
|
||||
This is the default mapping for the key labelled 'A' which normally has
|
||||
scancode 0x1E. The eight states is as shown, giving the 'A' key its
|
||||
scancode 0x1E. The eight states are as shown, giving the 'A' key its
|
||||
normal behavior.
|
||||
The spcl field is used to give the key "special" treatment, and is
|
||||
interpreted as follows.
|
||||
Each bit correspond to one of the states above. If the bit is 0 the
|
||||
Each bit corresponds to one of the states above. If the bit is 0 the
|
||||
key emits the number defined in the corresponding map[] entry.
|
||||
If the bit is 1 the key is "special". This means it does not emit
|
||||
anything, instead it changes the "state". That means it is a shift,
|
||||
anything; instead it changes the "state". That means it is a shift,
|
||||
control, alt, lock, switch-screen, function-key or no-op key.
|
||||
The bitmap is backwards ie. 7 for base, 6 for shift etc.
|
||||
|
||||
@ -94,7 +94,7 @@ The flgs field defines if the key should react on caps-lock (1),
|
||||
num-lock (2), both (3) or ignore both (0).
|
||||
|
||||
The kbdcontrol utility is used to load such a description into/outof
|
||||
the kernel at runtime. This make it possible to change the key
|
||||
the kernel at runtime. This makes it possible to change the key
|
||||
assignments at runtime, or more important to get (GIO_KEYMAP ioctl)
|
||||
the exact key meanings from the kernel (fx. used by the X server).
|
||||
|
||||
@ -113,7 +113,7 @@ The field keynum defines which function key that is programmed.
|
||||
The array keydef should contain the new string to be used (MAXFK long),
|
||||
and the length should be entered in flen.
|
||||
|
||||
The GETFKEY ioctl call works in a similar manner, execpt it returns
|
||||
The GETFKEY ioctl call works in a similar manner, except it returns
|
||||
the current setting of keynum.
|
||||
|
||||
The function keys are numbered like this:
|
||||
|
Loading…
Reference in New Issue
Block a user