Date: Thu, 26 May 2005 22:28:46 +0200 From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) To: Eric Anderson <anderson@centtech.com> Cc: Jeremie Le Hen <jeremie@le-hen.org>, Eric Kjeldergaard <kjelderg@gmail.com>, freebsd-current@freebsd.org, delphij@freebsd.org, Xin LI <delphij@delphij.net> Subject: Re: [CALL FOR TESTERS] VESA High Resolution Console support from DragonFly Message-ID: <867jhlk9z5.fsf@xps.des.no> In-Reply-To: <429468C3.5040207@centtech.com> References: <20050522112612.GA37841@frontfree.net> <20050523003843.GO850@obiwan.tataz.chchile.org> <1116815005.838.3.camel@spirit> <d9175cad05052421282f757528@mail.gmail.com> <1116999375.731.7.camel@spirit> <d9175cad0505242259265a12e8@mail.gmail.com> <429468C3.5040207@centtech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Eric Anderson <anderson@centtech.com> writes: > I noticed that changing to 16bit (instead of 32 or 24) helped a lot. ...because more pixels fit in a single 64 kB page, so the console code doesn't have to switch pages as much while redrawing the screen. Switching pages requires switching to virtual x86 mode (stalling the CPU and invalidating the cache) to invoke the VESA BIOS. On graphic adapters with linear framebuffer support (pretty much all of them today), you can map the entire framebuffer into memory to avoid paging, but our VESA driver doesn't know how to do that. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?867jhlk9z5.fsf>