[Bug 210382] Remove hardcoded maximum size (2048x1600) from vt(4) framebuffer

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Jun 20 08:37:49 UTC 2016


--- Comment #3 from Dave Cottlehuber <dch at skunkwerks.at> ---

I confirm this fixes the issue for me. The resulting console is slow, but the
size works fine again.

It should also allow closing #203376 (which I linked) and #202288 (which I
can't link but I mentioned this ticket in that one).

The clearing of the virtual consoles also works (at least for me on Apple /
Intel Iris Pro graphics) when using the new drm-next-4.6 branch.

Thanks Felix!

You are receiving this mail because:
You are the assignee for the bug.

More information about the freebsd-bugs mailing list