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: vesafb terminal for testing.
Date: Fri, 19 Aug 2005 02:48:38 +0200	[thread overview]
Message-ID: <200508190248.38363.okuji@enbug.org> (raw)
In-Reply-To: <200508141648.00325.okuji@enbug.org>

On Sunday 14 August 2005 16:48, Yoshinori K. Okuji wrote:
> On Sunday 14 August 2005 13:52, Vesa Jääskeläinen 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.

So I tested it and fixed/modified many things.

I changed the command names to vbeinfo and vbetest. More compatible with the 
traditional GRUB's naming scheme.

There were issues about the coding style. For example, a function definition 
must not be like this:

int
foo(int x)

but:

int
foo (int x)

Note the space character. This is the same for casts.

Also, you needed to use GRUB's error handling. In GRUB 2, the error is not 
only a constant value, but also a message. So, whenever appropriate, you 
should use the function grub_error. (This is a big improvement from GRUB 
Legacy, really.)

Please compare the files after my changes with yours for more details.

For now, I tested it only with qemu, and haven't tested the vesafb terminal 
yet.

Okuji



  parent reply	other threads:[~2005-08-19  1:01 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 [this message]
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
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=200508190248.38363.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.