Subject: Re: wsdisplay on vesafb is slow
To: None <firstname.lastname@example.org>
From: Jeremy C. Reed <email@example.com>
Date: 12/21/2006 16:05:19
On Thu, 21 Dec 2006, Christian Biere wrote:
> I'd suggest using VESAFB_DEPTH=8 for now. I tried 24 or 32 and then it gets
> really slow because obviously it has to copy 2/3/4x as much memory.
I don't use the console too much on this box.
I am using 16 because I am mostly using this under X.
(==) wsfb(0): Depth 16, (==) framebuffer bpp 16
I guess I could use 8 under X, but I recall something I used or did
before didn't like that.