Date: Tue, 14 Jul 2009 22:40:28 +0200 From: Ed Schouten <ed@80386.nl> To: Vladimir Grebenschikov <vova@fbsd.ru> Cc: freebsd-current@freebsd.org, Franck Royer <royerfranck@free.fr> Subject: Re: UTF-8 on 8.0-CURRENT: Yes We Can! Message-ID: <20090714204028.GT48776@hoeg.nl> In-Reply-To: <1247603171.2105.38.camel@localhost> References: <4A5C9CE2.6060801@free.fr> <20090714155513.GO48776@hoeg.nl> <1247599592.2232.27.camel@localhost> <20090714194726.GP48776@hoeg.nl> <1247603171.2105.38.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
--+ByKXx16ztm00L4d Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi Vladimir, * Vladimir Grebenschikov <vova@fbsd.ru> wrote: > In past graphical console draw text not too quick. > I've tried to live with VESA mode of sc (to match high resolution of > notebook display). But it was really slow. > Probably, your driver will be much faster ? Even though I like VESA, it's probably hard, if not impossible to get it working, mainly because we need vm86 to reprogram the hardware, which is not present on amd64. One of the things on my todo list is to figure out how the Intel hardware works, so we have an accelerated driver on those systems. This should also make it a lot more attractive to implement things like kernel modesetting somewhere in the future. Right now I'm using the VGA driver that Marcel Moolenaar wrote for vtc(4) in 2005. I basically made two optimisations: - Similar to syscons, I use a 25 Hz timer to refresh the modified portion of the screen, instead of handling input synchronously, like vtc(4) does. This timer will not be used during boot or while in the kernel debugger/experiencing a kernel panic. Writing data to the TTY will just store data in buffers, which means I can write data to the TTY at approximately 5 MB/sec on my 2.2 GHz MacBook. - I made some optimisation to prevent unneeded reads/writes to the VGA hardware. I have to say the speed is acceptable. Using my console driver in VMware Fusion is still a bit slow, but not driving you insane. Because it can't use the 25 Hz timer during boot, it takes some extra time to print the startup messages there. There is still room for improvement, so I suspect it won't be a problem by the time I'm done. --=20 Ed Schouten <ed@80386.nl> WWW: http://80386.nl/ --+ByKXx16ztm00L4d Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEARECAAYFAkpc7TwACgkQ52SDGA2eCwWRJACeMhUyIV6aVZN4q6NFV97RAsAx drUAn1uCgWW0S4F2SbiZ2kRhH6QCj0Wh =YUoG -----END PGP SIGNATURE----- --+ByKXx16ztm00L4d--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090714204028.GT48776>