Subject: Re: wsdisplay on vesafb is slow
To: None <email@example.com>
From: Michael Lorenz <firstname.lastname@example.org>
Date: 12/27/2006 04:19:41
-----BEGIN PGP SIGNED MESSAGE-----
On Dec 26, 2006, at 20:33, Thor Lancelot Simon wrote:
> On Mon, Dec 25, 2006 at 10:04:01PM -0800, Aaron J. Grier wrote:
>> On Thu, Dec 21, 2006 at 04:31:24PM -0500, Thor Lancelot Simon wrote:
>>> On Thu, Dec 21, 2006 at 03:58:18PM -0500, Michael Lorenz wrote:
>>>> There was a proposal for a VESA BIOS extension to talk to a blitter
>>>> but as far as I remember it never got anywhere.
>>> Can't it use VGA text mode for text, at least?
>> vesafb would cease to be a framebuffer, then, and isn't that the whole
>> point of vesafb?
>>> The problem is, with wscons attached to vesafb, the console is
>>> unusuably slow; with wscons attached to vga, and a direct-hardware-
>>> access X server, X11 is unsafe.
>> so pick your poison.
> That's an incredibly bogus non-answer. We already have wscons drivers
> that provide accellerated text rendering using hardware text modes
> also providing usable-by-X frame buffers.
That's an incredibly bogus non-answer - or since when do we have
accelerated wscons drivers for all possible chipsets that might come
with a VESA BIOS?
> What exactly is the excuse why vesafb must (according to you, and
> evidently Michael too) not work that way? The fact that it can't is
> responsible for a major longstanding security hole in the i386 port.
Well then go fix it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
-----END PGP SIGNATURE-----