Quoting Robert Millan <[EMAIL PROTECTED]>:
Now that I think of it, is there any reason for doing all the cmain()
cruft before grub_main() ? Getting to grub_main() only requires a working
stack, which we have, and grub_main() inmediately returns control back to
architecture-specific code in grub_machine_init().
So why not move from:
_start -> cmain -> grub_main
to:
_start -> grub_main -> grub_machine_init -> cmain
?
I think it would be great. We should try to make the code for
different architectures more uniform to simplify maintenance.
--
Regards,
Pavel Roskin
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/grub-devel
