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 14:52:24 +0100 [thread overview]
Message-ID: <87eke2qztz.fsf@student.han.nl> (raw)
In-Reply-To: <1111838991.4245510f6e902@imp6-q.free.fr> (Antoine Terrienne's message of "Sat, 26 Mar 2005 13:09:51 +0100")
Antoine Terrienne <antoine.terrienne@free.fr> writes:
> Ok so I guess we should change the getopt method used by grub-mkimage to argp
> too.
IMHO it should be changed for every utility in that case. If no one
knows argp, I could do that when I have some time and some other
issues are solved. That would be in some months, but it will be done.
> Oop sory I mean stdint.h
> Types like int32_t, uint32_t and intprt_t are defined from stdint.h
If that is used, you could replace int32_t by grub_uint32_t, etc.
> I try to send a new patch several times but it is too big for the mailing list
> size limit (100Kb) so I put it here :
> http://antoine.terrienne.free.fr/grub2/grub2_on_macosx_20050326.patch
Not including generated files will make the patch a lot smaller. I
personally don't have problems with big patches on the mailinglist.
Having the patch in the email will make it a lot easier for me to
review the patch.
> And the mail I sent with it :
>
> Here is a new patch much cleaner (with -u).
Please use -p as well. It will make reviewing the patch a *LOT*
easier.
> Everything compiles now but I didn't test It yet. In fact I don't know how to
> use and install grub2 on a drive. If you have and docs or info about installing
> a binary to be open firmware bootable that could help me, thanks ;-)
First you have to compile GRUB 2. After that you can use grub-mkimage
to create an ELF file that is loadable by open firmware. Using
grub-mkimage you should specify the name of the output executable and
which modules should be included. For testing you should at least include
apple.mod, ext2.mod, hfs.mod, ls.mod and normal.mod I think.
After that I just load it using "boot" or tftp.
> The compilation is OK but this patch is still ugly : I left the getopt. I add a
> flag -DGRUB_HOST to make a distinction between the host and build parts. The
> GRUB_HOST flag is only used in some specific powerpc include directories so it
> shouldn't affect the i386 part. I also add a grub_machine_fini in
> kern/powerpc/ieee1275/init.c needed by kern/loader.c. Right now
> grub_machine_fini is empty but it should call for someting like
> grub_console_fini (not present in powerpc part) and grub_ofdisk_fini (not
> implemented). I left malloc as an alternative to memalign. As far as I look in
> the code memalign is used to align memory segment from elf files and every
> usual cases in elf segments fits in the 16 byte alignment. So it should work
> well for now waiting for a better implementation to support exotic segment
> alignments.
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.
> Compilation and installation are OK. I get grub-emu grub-mkimage and every
> modules in the share/grub/ directory and grub-mkimage can produce images. Still
> need test and improvements but it seems to work.
Cool! please check if your modification did not add any warnings or
so, we would like to keep GRUB quite clean.
A complete review has to follow... sorry...
Thanks,
Marco
next prev parent reply other threads:[~2005-03-26 14:28 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 [this message]
2005-03-26 14:55 ` Antoine Terrienne
2005-03-26 15:20 ` Marco Gerards
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=87eke2qztz.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.