From: Marco Gerards <metgerards@student.han.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Kernel support for VESA Bios Extension
Date: Thu, 14 Jul 2005 23:45:36 +0200 [thread overview]
Message-ID: <87hdex5af3.fsf@student.han.nl> (raw)
In-Reply-To: <42D6CCE5.5010807@nic.fi> ( Vesa Jääskeläinen's message of "Thu, 14 Jul 2005 23:36:53 +0300")
Vesa Jääskeläinen <chaac@nic.fi> writes:
>>>I would like to hear comments about the patch. I tried to implement
>>>most commonly needed functions, so you can't do everything with
>>>this. As I didn't need to use every function in my frame buffer
>>>console test, some things might not work. But I tried to make my best
>>>to proof read every function.
>> Can you please make sure you are using the GCS for coding style?
>> Please have a look at the other sourcecode and the GCS (GNU Coding
>> Standards) first:
>> http://www.gnu.org/prep/standards/
>> It is important for us to have a single and consistent coding style.
>> If you have questions about either GRUB or the coding style you are of
>> course free to ask.
>
> Perhaps this is a bit closer to requirement?
It is, thanks.
> If there still are issues on formatting could you specify what issues
> you are thinking on.
Of course.
> +typedef grub_uint32_t grub_vbe_farptr_t;
> +typedef grub_uint32_t grub_vbe_physptr_t;
> +typedef grub_uint32_t grub_vbe_status_t;
Please use a single space before the type name.
> +struct grub_vbe_mode_info_block
> +{
> + /* Mandory information for all VBE revisions */
After the comment add a `.' and two spaces instead of one. This is
true for all comments.
> + /*
> + * Reserved field to make structure to be 256 bytes long, VESA BIOS
> + * Extension 3.0 Specification says to reserve 189 bytes here but
> + * that doesn't make structure to be 256 bytes. So additional one is
> + * added here.
> + */
I personally prefer not using that many `*'s and believe it is not in
the GCS. But I think Okuji uses this as well, but I don't. Perhaps
we need our own guidelines for such things, I think consistency is
important. Okuji, what you you think?
> + grub_uint8_t reserved4[189+1];
Please put spaces around operators. So this should be:
grub_uint8_t reserved4[189 + 1]
* 31 24 19 16 7 0
> * ------------------------------------------------------------
> * | | |B| |A| | | |1|0|E|W|A| |
> - * | BASE 31..24 |G|/|0|V| LIMIT |P|DPL| TYPE | BASE 23:16 |
> + * | BASE 31..24 |G|/|L|V| LIMIT |P|DPL| TYPE | BASE 23:16 | 4
> * | | |D| |L| 19..16| | |1|1|C|R|A| |
> * ------------------------------------------------------------
> * | | |
> - * | BASE 15..0 | LIMIT 15..0 |
> + * | BASE 15..0 | LIMIT 15..0 | 0
> * | | |
> * ------------------------------------------------------------
> *
What is this? Is this copied from (copyrighted) documentation?
To me it seemed line some lines were too long. Please keep in mind it
should be all readable on a 80 columns width terminal according to the
GCS.
I will be gone this weekend. After the weekend I will try to
understand the patch and proofread the assembler code. But my x86
assembly is *very* rusty, so I hope someone else can review this patch
because I am afraid when it comes to assembler my opinion is not worth
a bit. ;)
Thanks,
Marco
next prev parent reply other threads:[~2005-07-14 22:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 18:36 [PATCH] Kernel support for VESA Bios Extension Vesa Jääskeläinen
2005-07-14 19:02 ` Marco Gerards
2005-07-14 20:36 ` Vesa Jääskeläinen
2005-07-14 21:45 ` Marco Gerards [this message]
2005-07-15 10:53 ` Yoshinori K. Okuji
2005-07-15 16:47 ` Vesa Jääskeläinen
2005-07-15 18:55 ` Yoshinori K. Okuji
2005-07-16 18:43 ` Marco Gerards
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=87hdex5af3.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.