From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: generic BIOS-less boot (Re: [PATCH] New x86_64 EFI patch)
Date: Sat, 19 Jul 2008 17:01:43 +0200 [thread overview]
Message-ID: <20080719150143.GC23778@thorin> (raw)
In-Reply-To: <ca0f59980807121105u5bcf8c90n6a9229ca77013253@mail.gmail.com>
On Sun, Jul 13, 2008 at 02:05:13AM +0800, Bean wrote:
>
> Hi,
>
> Here are the information gathered in real mode:
>
> memory map information
> video information
> monitor information (edid)
> hard disk information
> perhaps more
>
> The first two can be retrieved in grub, others are optional, kernel
> can normally get the value itself.
>
> Perhaps we can write a generic protected mode linux loader for i386.
> Functions such as claiming memory, getting memory map and the like can
> be wrapped in platform dependent call arch_xxx.
I was wondering if maybe it would be simpler to emulate the BIOS (and use
stubs where suitable). Memory map would be simple to produce since we
already have this information which we used to initialize our heap. As
for video information, do you have more details (or know a document that
explains what's probed for)? If it's only for vesa modes maybe we could
just stub it.
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What good is a phone call… if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2008-07-19 15:02 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 17:04 [PATCH] New x86_64 EFI patch Bean
2008-06-21 17:04 ` Bean
2008-06-23 11:58 ` Isaac Dupree
2008-06-23 12:53 ` Bean
2008-06-24 12:52 ` Isaac Dupree
2008-06-24 13:12 ` Bean
2008-06-24 16:57 ` Isaac Dupree
2008-06-24 17:11 ` Bean
2008-06-24 21:59 ` Isaac Dupree
2008-06-25 6:49 ` Bean
2008-06-25 12:50 ` Isaac Dupree
2008-06-25 13:54 ` Bean
2008-06-28 10:51 ` Isaac Dupree
2008-06-28 11:55 ` Bean
2008-06-29 23:55 ` Isaac Dupree
2008-06-30 5:05 ` Bean
2008-07-02 13:43 ` Bean
2008-07-05 23:02 ` Isaac Dupree
2008-07-06 4:31 ` Bean
2008-07-08 16:16 ` Isaac Dupree
2008-07-08 16:31 ` Bean
2008-07-12 14:41 ` Robert Millan
2008-07-12 15:16 ` Bean
2008-07-12 15:26 ` Bean
2008-07-12 17:10 ` Robert Millan
2008-07-12 18:05 ` Bean
2008-07-17 9:50 ` Bean
2008-07-17 15:02 ` Javier Martín
2008-07-17 15:18 ` Bean
2008-07-17 15:28 ` Pavel Roskin
2008-07-17 15:22 ` Pavel Roskin
2008-07-17 15:26 ` Bean
2008-07-17 15:45 ` Javier Martín
2008-07-17 15:50 ` Bean
2008-07-17 16:01 ` Javier Martín
2008-07-17 16:17 ` Pavel Roskin
2008-07-17 16:06 ` Pavel Roskin
2008-07-17 16:17 ` Javier Martín
2008-07-19 15:01 ` Robert Millan [this message]
2008-07-12 15:26 ` Robert Millan
2008-07-12 15:37 ` Bean
2008-07-12 15:48 ` Bean
2008-06-25 12:59 ` Isaac Dupree
2008-07-03 18:11 ` Marco Gerards
2008-07-03 19:51 ` 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=20080719150143.GC23778@thorin \
--to=rmh@aybabtu.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.