From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: Bean <bean123ch@gmail.com>
Subject: Re: My implementation of the grub2 boot rom
Date: Sun, 23 Aug 2009 14:09:25 +0200 [thread overview]
Message-ID: <20090823120925.GR4130@thorin> (raw)
In-Reply-To: <ca0f59980712021219u195c437aj4eb33a09ef32005e@mail.gmail.com>
Hi Bean,
It appears this has been overlooked for quite a while. If you could resync
and re-send it as a patch, I'll be glad to review and see about getting it
merged.
On Mon, Dec 03, 2007 at 04:19:12AM +0800, Bean wrote:
> Hi,
>
> I've written my own code for grub2 boot rom, the steps are:
>
> 1, Use make to compile romboot.S and grub-mkrom.c, it will generate
> romboot.img and grub-mkrom.
> 2, Create kernel image core.img with grub-mkimage
> 3, Create rom image with grub-mkrom, like this:
>
> grub-mkrom romboot.img core.img output_file
>
> grub-mkrom support the following options:
>
> -m message Boot message
> -t timeout Timeout in seconds
> -k key Hotkey
> -x edx Value of EDX
>
> default hotkey is SPACE, default timeout is 2 seconds.
>
> The new code is much smaller than the romos version (only 240 bytes),
> and it runs grub2 after POST, so that int 13 can be used to access the
> disk.
>
> --
> Bean
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
--
Robert Millan
The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
how) you may access your data; but nobody's threatening your freedom: we
still allow you to remove your data and not access it at all."
prev parent reply other threads:[~2009-08-23 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-02 20:19 My implementation of the grub2 boot rom Bean
2009-08-23 12:09 ` Robert Millan [this message]
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=20090823120925.GR4130@thorin \
--to=rmh@aybabtu.com \
--cc=bean123ch@gmail.com \
--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.