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: Grub2 on Mac OS X
Date: Sat, 26 Mar 2005 16:20:50 +0100	[thread overview]
Message-ID: <878y4aqvql.fsf@student.han.nl> (raw)
In-Reply-To: <1111848950.424577f63f35d@imp6-q.free.fr> (Antoine Terrienne's message of "Sat, 26 Mar 2005 15:55:50 +0100")

Antoine Terrienne <antoine.terrienne@free.fr> writes:

Hi Antoine,

>> If that is used, you could replace int32_t by grub_uint32_t, etc.
> ok I was wondering if here were a specific reason for using both grub_int32_t
> and int32_t types like one for the host part and one for the build part. But if
> we can always use grub_xxx types it will make it a lot easier.

The reason was that this code was part of another project.  It has
been put into GRUB 2 and I think I missed these int32_t thingies.

>> I thought GRUBOF was not used anymore, but I see you replaced it.  I
>> hope I can find some time to have a look at your patch soon, but
>> please understand if it will take a while.
>>
>
> Yes GRUBOF have been removed from everywere exept in one .h file in the powerpc
> part. Must have been forgotten. In fact many little problems like this one
> seems to come from some great improvements made to Grub2-i386 that have not
> been ported to the powerpc part.

What kind of things do you think there are missing for the PPC port?
It should be quite complete by now.  It does not compile at the
moment, but this will be fixed in CVS really soon.

>>
>> Cool!  please check if your modification did not add any warnings or
>> so, we would like to keep GRUB quite clean.
>>
>
> most warnings come from the memcpy function that conflicts with the gcc builtin.

Can you show us?

>> A complete review has to follow... sorry...
>>
>
> No problem there's no rush.
> By the way I will probably put a more complete patch in a few days with all your
> remarks.

Cool.

Thanks,
Marco




  reply	other threads:[~2005-03-26 16:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-23 13:20 Grub2 on Mac OS X antoine terrienne
2005-03-23 20:45 ` Yoshinori K. Okuji
2005-03-23 22:28   ` Antoine Terrienne
2005-03-26  0:22     ` Yoshinori K. Okuji
2005-03-26 12:09       ` Antoine Terrienne
2005-03-26 13:52         ` Marco Gerards
2005-03-26 14:55           ` Antoine Terrienne
2005-03-26 15:20             ` Marco Gerards [this message]
2005-03-26 19:49               ` Antoine Terrienne
2005-03-26 20:09                 ` Marco Gerards
2005-03-26 13:40       ` Marco Gerards
  -- strict thread matches above, loose matches on Subject: below --
2005-03-21 18:55 Antoine Terrienne
2005-03-22 20:20 ` Yoshinori K. Okuji
2005-03-23 20:42   ` Brian Sammon
2005-03-23 21:09     ` Yoshinori K. Okuji
2005-03-26 13:37       ` 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=878y4aqvql.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.