Additional logging

Log when PROBE_DETECT bails and other.
Corrected pScrn->videoRam values

pScrn->videoRam is in kilobytes not bytes.
Corrected driver name

It was still set to netbsd's wsdisplay.
Hint about device

Comments about what the device normally is
Dump info about current video mode when DEBUG

Print details about the current video mode for the framebuffer
when compiled with DEBUG
Simplified framebuffer size calculation

Since this driver is for use with VGA mode exclusively (being an
Xorg driver), there is no need for the complicated depth logic
which was required when the textmode options existed.
Fixed still-not-understood issue with segfault at higher resolutions

* Added comments explaining odd behavior
* Using sysconf(_SC_PAGESIZE) instead of deprecated getpagesize()
* More output/state logging added
Trailing line ending

Removed excess blank lines/nulls
Tentative code to get and set VGA mode

Using FBIO_FINDMODE combined with FBIO_SETMODE to determine the correct
VGA mode value to use in order to set the screen resolution.
Hard-coded for now, will need to read from X config in the future.
Set resolution from environment variable $RESOLUTION

Determine the resolution to be set from an environment variable $RESOLUTION
Useful for passing a resolution in via `vidcontrol` output manipulation.
Format of $RESOLUTION is WIDTHxHEIGHTxDEPTH (e.g. 1280x800x32)

If no $RESOLUTION variable is detected, a default resolution of 1024x768x32
will be used instead.
Fixed display corruption at certain resolutions

For certain resolutions (e.g. 1366x768x32), the display would be corrupted
because of an error in the calculation of line bytes, e.g. each line would
start at an incorrect offset leading to an accumulatively-skewing output.
Better error message for unsupported modes

Contrary to what you'd expect, FBIO_FINDMODE fails completely when an
unsupported video mode is passed in, instead of returning a structure that
indicates the mode was not found. Detecting this and displaying the
appropriate error message accordingly.
Corrected calculation of video ram (cosmetic?)

Corrected a rounding error in the calculation of the video ram size.
I believe this was only used for display purposes (esp. since it was in KiB
instead of in bytes), but anyway...