Kazutaka YOKOTA writes:
In order to reflect the recent changes regarding syscons, keyboard and
video drivers, I wrote the following new man pages and update for a
couple of existing ones. They are rudimentary, but better than
nothing.
http://www.freebsd.org/~yokota/man4update.tar.gz
I've added a couple of tweaks. For some reason the .Fx macro
doesn't work on my terminal (using nroff -man foo.4), it just
replaces the O/S version with nothing.. so I used .Tn instead
which is what the pnpinfo(8) man page uses.
-Archie
___
Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com
diff -ur old/atkbd.4 new/atkbd.4
--- old/atkbd.4 Thu Feb 4 05:45:09 1999
+++ new/atkbd.4 Thu Feb 4 18:41:41 1999
@@ -69,7 +69,8 @@
The
.Nm
driver first appeared in
-.Fx 3.1 .
+.Tn FreeBSD
+3.1.
.Sh AUTHORS
The
.Nm
diff -ur old/atkbdc.4 new/atkbdc.4
--- old/atkbdc.4Thu Feb 4 05:45:10 1999
+++ new/atkbdc.4Thu Feb 4 18:43:06 1999
@@ -77,9 +77,11 @@
The
.Nm
driver first appeared in
-.Fx 3.1 .
+.Tn FreeBSD
+3.1.
It is based on the kbdio module in
-.Fx 2.2 .
+.Tn FreeBSD
+2.2.
.Sh AUTHORS
The kbdio module and the
.Nm
diff -ur old/splash.4 new/splash.4
--- old/splash.4Thu Feb 4 05:45:15 1999
+++ new/splash.4Thu Feb 4 18:48:38 1999
@@ -30,8 +30,8 @@
.Fl c
or
.Fl v
-boot option when loading kernel, the splash image won't appear.
-(But is still loaded and can be used as a screen saver later; see below.)
+boot option when loading kernel, the splash image won't appear
+(though it is still loaded and can be used as a screen saver later; see below).
.Pp
In order to display the bitmap, the bitmap file itself and
matching splash image decoder must be loaded by the boot loader.
@@ -41,7 +41,7 @@
.It splash_bmp.ko
W*ndows BMP file decoder.
While the BMP file format allows various depth of colors, this decoder
-can handle 256 color bitmaps only.
+can only handle 256 color bitmaps.
Other color depth won't work.
.El
.Pp
@@ -122,11 +122,11 @@
The screen saver won't run if the current screen is not in the
text mode.
.Sh SPLASH SCREEN AS A SCREEN SAVER
-If you load splash image but don't load a screen saver,
+If you load a splash image but don't load a screen saver,
you can continue using the splash module as a screen saver.
Specify the screen blanking interval as explained in the
.Sx SCREEN SAVER
-section above, then
+section above, and
the splash screen image will come back after the specified time.
.\.Sh DRIVER CONFIGURATION
.Sh FILES
@@ -188,7 +188,7 @@
.Xr pcvt 4 .
.Sh BUGS
If you load a screen saver while another screen saver has already
-been loaded, the first screen saver won't be automatically unloaed
+been loaded, the first screen saver won't be automatically unloaded
and remain in memory, wasting kernel memory space.
.Sh SEE ALSO
.Xr vidcontrol 1 ,
@@ -197,12 +197,13 @@
.Xr loader.rc 5 ,
.Xr rc.conf 5 ,
.Xr kldload 8 ,
-.Xr kldunload 8 ,
+.Xr kldunload 8 .
.Sh HISTORY
The
.Nm
driver first appeared in
-.Fx 3.1 .
+.Tn FreeBSD
+3.1.
.Sh AUTHORS
The
.Nm
diff -ur old/vga.4 new/vga.4
--- old/vga.4 Thu Feb 4 05:45:18 1999
+++ new/vga.4 Thu Feb 4 18:52:40 1999
@@ -50,7 +50,7 @@
option is required in the kernel configuration file in this case too.
.Sh DRIVER CONFIGURATION
.Ss Kernel Configuration Options
-There are following kernel configuration options to control the
+The following kernel configuration options control the
.Nm
driver.
They may be set in the kernel configuration file
@@ -81,7 +81,7 @@
option.
.It Em VESA_DEBUG=N
Set the VESA support debug level to N.
-The default value is zero and all debugging output is suppressed.
+The default value is zero (all debugging output is suppressed).
.El
.Pp
The following options will remove some features from the
@@ -128,14 +128,18 @@
.Sh SEE ALSO
.Xr syscons 4 ,
.Xr kldload 8 ,
-.Xr kldunload 8
+.Xr kldunload 8 .
.Sh STANDARD
-``VESA BIOS Extension (VBE)'', Video Electronics Standards Association.
+.Rs
+.%T VESA BIOS Extension (VBE)
+.%A Video Electronics Standards Association
+.Re
.Sh HISTORY
The
.Nm
driver first appeared in
-.Fx 3.1 .
+.Tn FreeBSD
+3.1.
.Sh AUTHORS
The
.Nm
To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-current in the body of the message