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: Tue, 16 Aug 2005 12:04:18 +0200	[thread overview]
Message-ID: <874q9qnqot.fsf@student.han.nl> (raw)
In-Reply-To: <43010B92.3030900@nic.fi> ( Vesa Jääskeläinen's message of "Tue, 16 Aug 2005 00:39:30 +0300")

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

> Marco Gerards wrote:
>> Vesa Jääskeläinen <chaac@nic.fi> writes:
>> 
>>>> There are some long lines, can you please make them shorter so
>>>> the maximal line length is 78 characters?
>>> Hmm... I made another scan for those. Still I left some of those there
>>> because in my opinion it is much more readable in that way. But splitted
>>> some lines.
>> 
>> Can you should me which so I can come up with a suggestion?
>
> video/i386/pc/vbe.c:
> - setpixel functions. There are couple of "too" long lines.
> - grub_vbe_get_video_mode_info first variable definition is a bit long.

      grub_uint32_t *ptr = (grub_uint32_t *)(framebuffer + y * bytes_per_scan_line + x * 4);

This can be changed in:

      grub_uint32_t *ptr;
      ptr = (grub_uint32_t *)(framebuffer + y * bytes_per_scan_line + x * 4);

or:

      grub_uint32_t *ptr = (grub_uint32_t *)(framebuffer + y *
                                             bytes_per_scan_line
                                             + x * 4);


> term/i386/pc/vesafb.c:
> - grub_virtual_screen_setup, grub_malloc line.

You fixed this already.  Please put operators on the beginning of the
next line instead of the end of the line.

> - write_char, set pixel line at end.

How about:

          grub_vbe_set_pixel_index(i + (virtual_screen.cursor_x
                                        * virtual_screen.char_width),
                                   y + (virtual_screen.cursor_y
                                        * virtual_screen.char_height),
                                   color);


> - grub_virtual_screen_setcolor, function definition.

This is a tough one, but not important I guess. :)


> commands/i386/pc/vbe_test.c:
> - GRUB_MOD_INIT.

You can split the line after the commas.

> commands/i386/pc/vbe_list_modes.c:
> - GRUB_MOD_INIT.

Same here.

> include/grub/i386/pc/vbe.h:
> - several function prototypes.

You could try to split the line after the commas for the arguments.
Sometimes it is not possible to create a shorter line and in that case
it is not important.

>>> I will scan the code once more and then commit a bit different version
>>> to CVS as Okuji asked to commit it to there for easier testing.
>
> Just a note until admins fix those commit messages, first version of vbe
> terminal support is now committed. It still needs more work, but it is a
> starting point.

Cool!  If you do receive the commit messages, can you forward them so
we could see them as well?

Thanks,
Marco




  reply	other threads:[~2005-08-16 10:53 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
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 [this message]
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=874q9qnqot.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.