<feed xmlns='http://www.w3.org/2005/Atom'>
<title>src-test2/sys/dev/vt, branch release/11.4.0</title>
<subtitle>FreeBSD source tree</subtitle>
<id>https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F11.4.0</id>
<link rel='self' href='https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F11.4.0'/>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/'/>
<updated>2020-04-25T15:27:45Z</updated>
<entry>
<title>MFC r359626: vt: avoid overrun when stride is not a multiple of bytes per pixel</title>
<updated>2020-04-25T15:27:45Z</updated>
<author>
<name>Ed Maste</name>
<email>emaste@FreeBSD.org</email>
</author>
<published>2020-04-25T15:27:45Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=e7cb9f8d635bac6d413ca99f48bd8f7a9fae776d'/>
<id>urn:sha1:e7cb9f8d635bac6d413ca99f48bd8f7a9fae776d</id>
<content type='text'>
The reporter is developing a frame buffer driver for hardware using
3 bytes per pixel, but a stride that's a multiple of 256.  Previously
this resulted in writing beyond the end of each stride.  On the last
row this attempted to write past the end of the frame buffer, triggering
the assertion in vt_fb_mem_wr1().

PR:		243533
Submitted by:	Thomas Skibo
</content>
</entry>
<entry>
<title>MFC r355935: vt: fix post-boot keyboard attachment</title>
<updated>2019-12-23T20:19:23Z</updated>
<author>
<name>Kyle Evans</name>
<email>kevans@FreeBSD.org</email>
</author>
<published>2019-12-23T20:19:23Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=64988970956ba73bbad6bce97d55b74da3a884f0'/>
<id>urn:sha1:64988970956ba73bbad6bce97d55b74da3a884f0</id>
<content type='text'>
With absolutely no keyboards attached and no kbdmux in kernel, we descend
down this error path. 0 is a valid keyboard index, so leaving
vd-&gt;vd_keyboard at 0 when there's no keyboard found is objectively wrong as
later attachment of a keyboard will fail -- it gets index 0, and vt thinks
it's already using that keyboard.

This is decidedly the corniest of corner cases, but it's easy enough to get
correct that we should do so.

Tested in a kernel without atkbdc, atkbd, psm, kbdmux, ukbd, hyperv then
loading ukbd post-boot and attaching a usb keyboard.
</content>
</entry>
<entry>
<title>MFC r348059: vt efifb: add suspend/resume calls</title>
<updated>2019-12-16T18:04:31Z</updated>
<author>
<name>Ed Maste</name>
<email>emaste@FreeBSD.org</email>
</author>
<published>2019-12-16T18:04:31Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=78d126024499098beadcd1cdd9aabad897eabcac'/>
<id>urn:sha1:78d126024499098beadcd1cdd9aabad897eabcac</id>
<content type='text'>
PR:		237050
Submitted by:	Erik Kurzinger &lt;ekurzinger@nvidia.com&gt;
</content>
</entry>
<entry>
<title>MFC r353680: vt: remove comment that is not true since r259680</title>
<updated>2019-10-23T14:16:34Z</updated>
<author>
<name>Ed Maste</name>
<email>emaste@FreeBSD.org</email>
</author>
<published>2019-10-23T14:16:34Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=7688dcbe186124ce6a9f185fe98cfaaab3fd4eee'/>
<id>urn:sha1:7688dcbe186124ce6a9f185fe98cfaaab3fd4eee</id>
<content type='text'>
r259680 added support to vt(4) for printing double-width characters.
Remove comment that claims no support.

Sponsored by:	The FreeBSD Foundation
</content>
</entry>
<entry>
<title>MFC r352505: vt: fix problems with trying to switch to a closed VT</title>
<updated>2019-09-30T13:34:30Z</updated>
<author>
<name>Andriy Gapon</name>
<email>avg@FreeBSD.org</email>
</author>
<published>2019-09-30T13:34:30Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=163d633f0cbe0005eb18dc4fec3498ae4c8aa9f6'/>
<id>urn:sha1:163d633f0cbe0005eb18dc4fec3498ae4c8aa9f6</id>
<content type='text'>
</content>
</entry>
<entry>
<title>MFC r349834</title>
<updated>2019-07-16T16:49:11Z</updated>
<author>
<name>Eric van Gyzen</name>
<email>vangyzen@FreeBSD.org</email>
</author>
<published>2019-07-16T16:49:11Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=9feec24d049236d6f8a197dad833057c091d9c9e'/>
<id>urn:sha1:9feec24d049236d6f8a197dad833057c091d9c9e</id>
<content type='text'>
Ignore kern.vt.splash_cpu without graphics

When the system has no graphical console, such as bhyve in common
configurations, ignore kern.vt.splash_cpu, instead of panicking
on INVARIANTS kernels.

Reviewed by:	cem dumbbell
Sponsored by:	Dell EMC Isilon
Differential Revision:	https://reviews.freebsd.org/D20877
</content>
</entry>
<entry>
<title>MFC r342639:</title>
<updated>2019-04-22T13:55:06Z</updated>
<author>
<name>Ian Lepore</name>
<email>ian@FreeBSD.org</email>
</author>
<published>2019-04-22T13:55:06Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=e2a201fcb675f401bde7b74552345ca152eac898'/>
<id>urn:sha1:e2a201fcb675f401bde7b74552345ca152eac898</id>
<content type='text'>
When allocating a new keyboard at vt_upgrade() time, unwind any cngrabs
done on the old keyboard and then do the corresponding number of grabs
on the new keyboard.

This fixes a race that can leave the system with a non-functioning
keyboard.  It goes like this...

 - The bios claims there is an AT keyboard, atkbd attaches.
 - SI_SUB_INT_CONFIG_HOOKS runs.
 - USB probes devices. Devices begin attaching, including disks.
 - GELI prompts for a password for a just-attached disk, which results
   in a cngrab() while atkbd is the keyboard.
 - A USB keyboard attaches.
 - vt_upgrade() runs and switches the keyboard to the new USB keyboard,
   but because cngrab was never called for it, it's not activated and
   keystrokes are ignored.
 - Now there is no functional keyboard and no way to get one; even
   plugging in a different USB keyboard doesn't help, because the console
   is still grabbed, still waiting for a GELI pw.
</content>
</entry>
<entry>
<title>MFC r335631:</title>
<updated>2018-07-29T05:14:26Z</updated>
<author>
<name>Eitan Adler</name>
<email>eadler@FreeBSD.org</email>
</author>
<published>2018-07-29T05:14:26Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=271a27beaa46277207571aa31cf38b412463b431'/>
<id>urn:sha1:271a27beaa46277207571aa31cf38b412463b431</id>
<content type='text'>
Always initialize the ignore local variable.
PR:		229235
</content>
</entry>
<entry>
<title>MFC r335629:</title>
<updated>2018-07-28T07:37:01Z</updated>
<author>
<name>Eitan Adler</name>
<email>eadler@FreeBSD.org</email>
</author>
<published>2018-07-28T07:37:01Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=a62e1052ce031f5f224b931e2ec44ae35406ea7e'/>
<id>urn:sha1:a62e1052ce031f5f224b931e2ec44ae35406ea7e</id>
<content type='text'>
vt: add option to ignore NO_VGA flag in ACPI

To workaround buggy firmware that sets this flag when there's actually
a VGA present.

Ref D16003
PR:		229235
</content>
</entry>
<entry>
<title>MFC r332452: Update vt(4) "Terminus BSD Console" font to v4.46</title>
<updated>2018-04-19T00:40:34Z</updated>
<author>
<name>Ed Maste</name>
<email>emaste@FreeBSD.org</email>
</author>
<published>2018-04-19T00:40:34Z</published>
<link rel='alternate' type='text/html' href='https://cgit-dev.freebsd.org/src-test2/commit/?id=17d0f9fbc9301c489d0a4ebe03da2facc29ecf89'/>
<id>urn:sha1:17d0f9fbc9301c489d0a4ebe03da2facc29ecf89</id>
<content type='text'>
"Terminus BSD Console" is a derivative of Terminus that is provided
by Mr. Dimitar Zhekov under the 2-clause BSD license for use by the
FreeBSD vt(4) console and other BSDs.

PR:		227409
Sponsored by:	The FreeBSD Foundation
</content>
</entry>
</feed>
