Subject: Re: wsdisplay on vesafb is slow
To: None <tls@rek.tjls.com>
From: Michael Lorenz <macallan@netbsd.org>
List: current-users
Date: 12/27/2006 04:19:41
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

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 
> while
> 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.

have fun
Michael
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iQEVAwUBRZI6rspnzkX8Yg2nAQJeHAf+ObD0o3UTb62ohKtKRcRrkufGaAED4nlc
+2fPWWGgoeR+aSttout/NX/qja/8IzIe6t44LhR3fJ4d9S4Ar9a3DW1jyJPmDOsF
qCLu1gJoat9iVUni0CJ6iQ6oMA9EzWKbp5oL6LWvf45VfhZY1pavp7t+Ox8AY2il
v10LkIKCTxA38juj4F4ituVn1kG/XfzFTA/BhALzdnKNlkls2NcjdFu6podcdkpn
sPgN7S/B6lRsldF9I1wPlp2sdBdBA2WcjbrG5sthkdALHG3a+LKoklr2QmZLqJFt
6wrj1SttO+ZPvApOxJ6GwVPQVEtXqeJ3/eu1EEub+3uLeRiO+0sWbw==
=iNH5
-----END PGP SIGNATURE-----