Aren/NetBSD
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Whitespace, wording, typos.

Browse Source
This commit is contained in:
wiz 2012-07-19 10:27:58 +00:00
parent 1be9745405
commit a619892f93
1 changed files with 15 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
share/man/man4/tdvfb.4
View File

@ -1,4 +1,4 @@
.\" $NetBSD: tdvfb.4,v 1.1 2012/07/19 08:57:09 rkujawa Exp $
.\" $NetBSD: tdvfb.4,v 1.2 2012/07/19 10:27:58 wiz Exp $
.\"
.\" Copyright (c) 2012 Radoslaw Kujawa
.\" All rights reserved.
@ -38,7 +38,7 @@
The
.Nm
driver provides support for the 3Dfx Voodoo 2 graphics card and provides an
interface for machine independent
interface for the machine independent
.Xr wscons 4
driver.
.Pp
@ -46,10 +46,11 @@ Since Voodoo2 was originally designed as a 3D-only solution, most boards do not
have any kind of firmware.
The
.Nm
driver is albe to do low level initialization (boot) of the board, which means
driver is able to do low level initialization (boot) of the board, which means
that it can be used on all architectures and is truly machine independent.
However, it also means that driver is can not detect automatically if Voodoo2
However, it also means that driver is cannot detect automatically if Voodoo2
is used as a console.
The
.Dv TDVFB_CONSOLE
option is provided and should be set if the
.Nm
@ -75,21 +76,21 @@ driver was written by
were used as reference.
The
.Xr wscons 4
attachment code is based mostly on a
attachment code is based mostly on the
.Xr genfb 4
driver by
.An Michael Lorenz .
.Sh BUGS
The
.Nm
driver is unaccelerated. 3Dfx Voodoo2 has a simple 2D graphics engine but it is
unsupported yet.
.Nm
driver is unaccelerated.
3Dfx Voodoo2 has a simple 2D graphics engine but it is unsupported yet.
.Pp
Video mode is hard coded to 800x600 at 60Hz in 32-bits, it should be selectable
at least via kernel configuration file.
It is not possibe to detect what resolutions are supported by the monitor,
Video mode is hard-coded to 800x600 at 60Hz in 32-bits, it should be selectable
at least via kernel configuration file.
It is not possible to detect what resolutions are supported by the monitor,
since Voodoo2 has no DDC interface.
.Pp
8-bit depth is not supported by the hardware.
16-bit depth is supported by the hardware and is a prefered depth, however it
does not work corretly at the moment (this is a driver problem).
8-bit depth is not supported by the hardware.
16-bit depth is supported by the hardware and is the preferred depth, however it
does not work correctly at the moment (this is a driver problem).