From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] PXE support for grub2
Date: Tue, 05 Aug 2008 10:16:21 +0200 [thread overview]
Message-ID: <871w133mi2.fsf@xs4all.nl> (raw)
In-Reply-To: <ca0f59980808042036u275bb1acrcfd0050e28a2140d@mail.gmail.com> (bean123ch@gmail.com's message of "Tue, 5 Aug 2008 11:36:06 +0800")
Bean <bean123ch@gmail.com> writes:
>>> +GRUB_MOD_INIT(pxe)
>>> +{
>>> + (void) mod; /* To stop warning. */
>>> +
>>> + grub_pxe_detect ();
>>> + if (grub_pxe_pxenv)
>>> + {
>>> + grub_disk_dev_register (&grub_pxe_dev);
>>> + grub_fs_register (&grub_pxefs_fs);
>>
>> filesystems belong in fs/
>
> Perhaps I should place it in fs/i386/pc ?
I think it would make things clearer, although I am not too sure :-)
>>> +struct grub_pxenv
>>> +{
>>> + grub_uint8_t signature[6]; /* 'PXENV+' */
>>> + grub_uint16_t version; /* MSB = major, LSB = minor */
>>> + grub_uint8_t length; /* structure length */
>>> + grub_uint8_t checksum; /* checksum pad */
>>> + grub_uint32_t rm_entry; /* SEG:OFF to PXE entry point */
>>> + grub_uint32_t pm_offset; /* Protected mode entry */
>>> + grub_uint16_t pm_selector; /* Protected mode selector */
>>> + grub_uint16_t stack_seg; /* Stack segment address */
>>> + grub_uint16_t stack_size; /* Stack segment size (bytes) */
>>> + grub_uint16_t bc_code_seg; /* BC Code segment address */
>>> + grub_uint16_t bc_code_size; /* BC Code segment size (bytes) */
>>> + grub_uint16_t bc_data_seg; /* BC Data segment address */
>>> + grub_uint16_t bc_data_size; /* BC Data segment size (bytes) */
>>> + grub_uint16_t undi_data_seg; /* UNDI Data segment address */
>>> + grub_uint16_t undi_data_size; /* UNDI Data segment size (bytes) */
>>> + grub_uint16_t undi_code_seg; /* UNDI Code segment address */
>>> + grub_uint16_t undi_code_size; /* UNDI Code segment size (bytes) */
>>> + grub_uint32_t pxe_ptr; /* SEG:OFF to !PXE struct */
>>> +} __attribute__ ((packed));
>>
>> Can you GRUB-ify the comments here and below a bit?
>
> What do you mean by "GRUB-ify the comments" ?
". */
Although it is not too important for structs, I think :-)
--
Marco
next prev parent reply other threads:[~2008-08-05 8:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 16:50 [PATCH] PXE support for grub2 Bean
2008-08-01 3:46 ` Bean
2008-08-01 3:52 ` Pavel Roskin
2008-08-01 11:32 ` Robert Millan
2008-08-01 16:21 ` Pavel Roskin
2008-08-01 16:59 ` Bean
2008-08-02 4:34 ` Bean
2008-08-02 10:48 ` Robert Millan
2008-08-02 11:20 ` Bean
2008-08-02 11:49 ` Robert Millan
2008-08-04 21:08 ` Marco Gerards
2008-08-05 3:36 ` Bean
2008-08-05 8:16 ` Marco Gerards [this message]
2008-08-05 15:15 ` Bean
2008-08-06 6:18 ` Bean
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=871w133mi2.fsf@xs4all.nl \
--to=mgerards@xs4all.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.