All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: vesafb terminal for testing.
Date: Mon, 15 Aug 2005 19:24:19 +0200	[thread overview]
Message-ID: <87zmrjxge4.fsf@student.han.nl> (raw)
In-Reply-To: <42FF3097.7030904@nic.fi> ( Vesa Jääskeläinen's message of "Sun, 14 Aug 2005 14:52:55 +0300")

Vesa Jääskeläinen <chaac@nic.fi> writes:

Hi Vesa,

> 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).

Nice!  In this email I will propose some suggestions and comments on
the patch itself.

> There are couple of things that I do not like in this patch.
>
> 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.

Right, the video driver should be a new kind of interface.  It should
have functions to get/put pixels, boxes, whatever to the screen.  I am
not sure about video interfaces, but they should be simple and
generic.  In that case I can easily write a framebuffer for the PPC,
for example.

You should keep in mind that there are many depths (1, 4, 8, 16, 24 and
32 bits) that should be supported.  They all work differently.

> Second one is that this patch uses VGA BIOS fonts to draw characters and
> it might cause some problems in some cards.

We should use the font manager and nothing else IMO.

> 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=0x111')

I will test it soon.


Some comments on the patch:

>  2005-08-14  Vesa Jaaskelainen  <chaac@nic.fi>
>  
> +	* DISTLIST: Added term/i386/pc/vesafb.c
> +	* term/i386/pc/vesafb: New file.

Can you please split this up to the generic framebuffer terminal?  The
terminal for framebuffers should be generic and the videodrivers
should be arch specific.  Or do you want to do that later?

You forgot the ".c" on the last line.

> +
> +2005-08-14  Vesa Jaaskelainen  <chaac@nic.fi>
> +
>  	* DISTLIST: Added include/grub/i386/pc/vbe.h.

Why two changelog entries?  I do not see this change anywhere in the
patch.
  
> +static void
> +*real2pm(grub_vbe_farptr_t ptr)

The * is a part of the type, can you put it on the previous line?


There are some long lines, can you please make them shorter so
the maximal line length is 78 characters?

You sometimes use C++ style comments.  Can you change your comments so
they match the style described in the GCS:
http://www.gnu.org/prep/standards/html_node/Comments.html#Comments

Thanks,
Marco




  parent reply	other threads:[~2005-08-15 17:30 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-14 11:52 vesafb terminal for testing Vesa Jääskeläinen
2005-08-14 14:48 ` Yoshinori K. Okuji
2005-08-14 15:45   ` Vesa Jääskeläinen
2005-08-14 16:47     ` Vladimir Serbinenko
2005-08-14 19:25       ` Yoshinori K. Okuji
2005-08-15 15:23         ` Vincent Pelletier
2005-08-15 16:06           ` Vladimir Serbinenko
2005-08-15 17:02             ` Marco Gerards
2005-08-15 17:19             ` Yoshinori K. Okuji
2005-08-15 17:41               ` Marco Gerards
2005-08-15 18:55                 ` Yoshinori K. Okuji
2005-08-15 20:54                   ` Marco Gerards
2005-08-15 21:44               ` Vesa Jääskeläinen
2005-08-16  6:47               ` Vincent Pelletier
2005-08-16 10:20                 ` Marco Gerards
2005-08-15 17:07         ` Marco Gerards
2005-08-16  6:54           ` Vincent Pelletier
2005-08-14 21:48       ` Vesa Jääskeläinen
2005-08-14 22:19         ` Yoshinori K. Okuji
2005-08-15 15:52           ` Vesa Jääskeläinen
2005-08-15 16:13             ` Yoshinori K. Okuji
2005-08-15 15:42         ` Vladimir Serbinenko
2005-08-19  0:48   ` Yoshinori K. Okuji
2005-09-18 21:03     ` Vesa Jääskeläinen
2005-09-19 19:00       ` Yoshinori K. Okuji
2005-09-19 23:11         ` Vesa Jääskeläinen
2005-09-20 17:13           ` Yoshinori K. Okuji
2005-08-15 17:24 ` Marco Gerards [this message]
2005-08-15 21:05   ` Vesa Jääskeläinen
2005-08-15 21:21     ` Marco Gerards
2005-08-15 21:39       ` Vesa Jääskeläinen
2005-08-16 10:04         ` Marco Gerards
2005-08-16 18:36           ` Vesa Jääskeläinen

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=87zmrjxge4.fsf@student.han.nl \
    --to=metgerards@student.han.nl \
    --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.