freebsd-skq/sys/sparc64
marius 4a275767aa 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.

MFC after:	3 days
2016-09-06 22:18:08 +00:00
..
central Use OF_prop_free instead of direct call to free(9) 2016-05-18 23:39:31 +00:00
conf Disable vt(4) by default on sparc64 as creator_vt(4) and vt_ofwfb(4) 2016-09-06 22:18:08 +00:00
ebus Use OF_prop_free instead of direct call to free(9) 2016-05-18 23:39:31 +00:00
fhc Consistently use device_t 2016-08-09 19:32:06 +00:00
include Add new bus methods for mapping resources. 2016-05-20 17:57:47 +00:00
isa Use OF_prop_free instead of direct call to free(9) 2016-05-18 23:39:31 +00:00
pci sys: replace comma with semicolon when pertinent. 2016-08-09 19:42:20 +00:00
sbus Use OF_prop_free instead of direct call to free(9) 2016-05-18 23:39:31 +00:00
sparc64 Replace the number 4 in pmap_ts_referenced() by PMAP_TS_REFERENCED_MAX, 2016-09-04 22:08:04 +00:00