From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1E4K1v-0001rL-8m for mharc-grub-devel@gnu.org; Sun, 14 Aug 2005 11:04:07 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1E4K16-0001hH-N2 for grub-devel@gnu.org; Sun, 14 Aug 2005 11:03:17 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1E4K0y-0001ca-VJ for grub-devel@gnu.org; Sun, 14 Aug 2005 11:03:10 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1E4K0y-0001WE-JI for grub-devel@gnu.org; Sun, 14 Aug 2005 11:03:08 -0400 Received: from [212.43.237.68] (helo=kotoba.storever.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1E4K2V-0002h8-J1 for grub-devel@gnu.org; Sun, 14 Aug 2005 11:04:43 -0400 Received: from ASSP-nospam (localhost [127.0.0.1]) by kotoba.storever.com (Postfix) with ESMTP id E59FAFF65C04 for ; Sun, 14 Aug 2005 16:49:09 +0200 (CEST) Received: from 127.0.0.1 ([127.0.0.1] helo=ip6-localhost) by ASSP-nospam ; 14 Aug 05 14:49:09 -0000 From: "Yoshinori K. Okuji" Organization: enbug.org To: The development of GRUB 2 Date: Sun, 14 Aug 2005 16:48:00 +0200 User-Agent: KMail/1.7.2 References: <42FF3097.7030904@nic.fi> In-Reply-To: <42FF3097.7030904@nic.fi> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200508141648.00325.okuji@enbug.org> Subject: Re: vesafb terminal for testing. X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GRUB 2 List-Id: The development of GRUB 2 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Aug 2005 15:03:20 -0000 On Sunday 14 August 2005 13:52, Vesa J=E4=E4skel=E4inen wrote: > I have attached patch here that adds simple terminal that uses VESA BIOS > Extension 2.0+ for rendering terminal. It is not meant to be included as > is in GRUB 2, but I would hope that people would test it, so I could try > to improve it for greater compatibility (even though I have tried to > follow the standards, there might be some glitches between > implementations). That's great. I will try once I finish my current task. > First one is that there should be common virtual terminal for all arch's > and then separate graphics drivers that will do the actual drawing. In > this patch this is all implemented in one module and it is not as pretty > as it could be. Another way is to emulate VBE on other architectures... Actually, some=20 firmware (such as CFE) follows this way (e.g. CFE emulates PC's VGA BIOS). > Second one is that this patch uses VGA BIOS fonts to draw characters and > it might cause some problems in some cards. You should use the font manager to render characters, like the VGA terminal= =2E=20 Getting fonts from the BIOS is the last resort. > Third one is that there are some testing functionality (vbe_test, > vbe_list_modes) in same module, what would be best place to move those? I think they should be in the directory commands. These may be useful even= =20 when the user does not use a framebuffer terminal, because Multiboot=20 Specification also requires VBE support. > Now how to get started on testing: > - insmod vesafb > - Use vbe_list_modes to find mode number (eg. 0x111) that you want to use. > - set vbe_mode varible ('set vbe_mode=3D0x111') > > To test mode: > - vbe_test > > To use it in terminal: > - insmod terminal > - terminal vesafb Thank you for your description. Can we have your code in the CVS? It's easi= er=20 to test, once it is merged, because we do not have to care about conflicts. Okuji