All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: FIXME: These should be dynamically obtained from a terminal.
Date: Tue, 5 Jul 2005 01:05:54 +0200	[thread overview]
Message-ID: <200507050105.54961.okuji@enbug.org> (raw)
In-Reply-To: <42C85357.20500@yahoo.fr>

On Sunday 03 July 2005 23:06, Vincent Pelletier wrote:
> -add an asm function to get the current vga mode without changing it (or
> maybe a global var to keep the current vga mode)

Probably it is better to keep the current mode in a variable. It is not funny 
to go back to real mode every time.

> -add a field in struct grub_term
> -implement this function in different terminal handlers
> -implement grub_getwh
> -redefine GRUB_TERM_WIDTH & GRUB_TERM_HEIGHT macros to use grub_getwh

Sound good.

> Here are my questions :
> Should we foresee, in vga mode, that the user might someday choose his
> vga mode ?

No. Since the BIOS does not provide the geometry for each VGA mode, we must 
maintain a table in that case. And, the table differs among video cards. So I 
do not want to allow the user to change it to an arbitrary mode.

What we really need is to support VESA. The screen of the VGA mode is too 
small to do fancy stuff.

> Should we redefine all the macros we use to draw the menu to be less
> intensive on grub_getwh ?

We need to call grub_getwh only once. Possibly in grub_menu_init_page.

> In the attached patch, the vga function is disabled, because for now the
> asm function does not work (returns always 0). As I'm really not
> familiar with x86 asm, I think I had something wrong adapting from
> grub_vga_set_mode.

As the VGA mode is hardcoded, you can hardcode the geometry in vga.c as well.

BTW, is the VGA terminal working well? Since Marco changed the mode to 0x10 
from 0x12, the screen is a bit smaller than before, and I'm not sure if the 
menu entry editor works with this.

Okuji



  parent reply	other threads:[~2005-07-04 23:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-03 21:06 FIXME: These should be dynamically obtained from a terminal Vincent Pelletier
2005-07-03 21:16 ` [Bulk] " Vincent Pelletier
2005-07-04 23:05 ` Yoshinori K. Okuji [this message]
2005-07-04 23:19   ` Vincent Pelletier
2005-07-05 10:15   ` Marco Gerards
2005-07-05 15:56     ` Yoshinori K. Okuji
2005-07-05 16:26       ` Marco Gerards
2005-07-12 20:05         ` [PATCH] " Vincent Pelletier
2005-07-13  8:40           ` [PATCHv2] " Vincent Pelletier
2005-07-13 16:41             ` Marco Gerards
2005-07-13 21:29               ` Vincent Pelletier
2005-08-04 12:29                 ` Marco Gerards
2005-08-04 18:13                   ` Marco Gerards
2005-08-09  3:26                     ` Hollis Blanchard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200507050105.54961.okuji@enbug.org \
    --to=okuji@enbug.org \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.