diff options
author | marius <marius@FreeBSD.org> | 2017-05-10 20:53:13 +0000 |
---|---|---|
committer | marius <marius@FreeBSD.org> | 2017-05-10 20:53:13 +0000 |
commit | dcde69b03b85cf7ea79958caad181b7dcf93f7b4 (patch) | |
tree | 718bd75199a28625d17541d84d90e9634c5cb6a6 /sys/sparc64/conf | |
parent | 1477d32c8175c9dd8b564ec8b3057c8b7be41bac (diff) | |
download | FreeBSD-src-dcde69b03b85cf7ea79958caad181b7dcf93f7b4.zip FreeBSD-src-dcde69b03b85cf7ea79958caad181b7dcf93f7b4.tar.gz |
MFC: r305507
Disable vt(4) by default on sparc64 as creator_vt(4) and vt_ofwfb(4)
have the serious problem of not actually attaching the hardware they
are driving at the bus level. This causes creator(4) and machfb(4)
to attach and drive the very same hardware in parallel when both
syscons(4) and vt(4) as well as their associated hardware drivers
are built into a kernel, i. e. GENERIC, at the same time.
Also, syscons(4) and its drivers still are way superior to vt(4) and
its equivalents; unlike the syscons(4) counterparts the vt(4) drivers
don't provide hardware acceleration resulting in considerably slower
screen drawing, creator_vt(4) doesn't provide a /dev/fb node as
required by the Xorg sunffb(4) etc. In theory, vt_ofwfb(4) should be
able to handle more devices than machfb(4). However, testing shows
that it hardly works with any hardware machfb(4) isn't also able to
drive, making vt(4) and vt_ofwfb(4) not favorable for the time being
from that perspective either.
Diffstat (limited to 'sys/sparc64/conf')
-rw-r--r-- | sys/sparc64/conf/GENERIC | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/sys/sparc64/conf/GENERIC b/sys/sparc64/conf/GENERIC index 15cf021..e593e18 100644 --- a/sys/sparc64/conf/GENERIC +++ b/sys/sparc64/conf/GENERIC @@ -138,7 +138,7 @@ device splash # Splash screen and screen saver support options KBD_INSTALL_CDEV # install a CDEV entry in /dev # vt is the new video console driver -device vt +#device vt # Builtin hardware device auxio # auxiliary I/O device |