From: "H. Peter Anvin" <hpa@zytor.com>
To: Brandon Falk <bfalk@gamozolabs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [question] x86/x86_64 boot process
Date: Tue, 12 Jun 2012 14:05:40 -0700 [thread overview]
Message-ID: <4FD7AF24.8080607@zytor.com> (raw)
In-Reply-To: <CAK9+cJX9GHjToKbOqqmink5Kr-9y3ZhQPC8M8rcL70rWbbYVYw@mail.gmail.com>
On 06/12/2012 01:49 PM, Brandon Falk wrote:
> Greetings. Please CC me on any responses as I do not subscribe to the list.
>
> I'm currently working on a very very small boot loader. Currently it
> uses BIOS int 0x13 to load up the 'setup' segments to 0x9000:0x0000. I
> jump to this location, set up the kernel options, and then jump to
> 0x9020:0x0000. Everything goes great. However, I get the message 'No
> setup signature found...'. I'm assuming this is due to not loading up
> the protected-mode code. I'm slightly confused as to how the protected
> mode code is to be loaded. As my 'bzImage' is 2.6MB, I would need to
> raise the A20 line to possibly load this up. Does the kernel assist in
> this process at all? Should I set up a code32_start routine for my
> code to load up the kernel? Once I'm in protected mode, how will I
> even access the medium that the kernel is loaded from without creating
> a driver?
>
> Currently the medium is a floppy image loaded in VMWare. It's a 64-bit
> system. I'm just looking to be pointed in the right direction for the
> next step (and if my current steps are valid for Protocol 2.10).
>
> Here's the current code (the code is manually overwritten onto the
> bzImage, however only the code... the headers are left intact on the
> bzImage):
>
Please read Documentation/x86/boot.txt.
-hpa
next prev parent reply other threads:[~2012-06-12 21:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-12 20:49 [question] x86/x86_64 boot process Brandon Falk
2012-06-12 21:05 ` H. Peter Anvin [this message]
2012-06-12 21:14 ` Brandon Falk
2012-06-12 21:15 ` H. Peter Anvin
2012-06-12 21:16 ` H. Peter Anvin
2012-06-12 21:20 ` Brandon Falk
2012-06-12 21:33 ` Brandon Falk
2012-06-12 21:37 ` H. Peter Anvin
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=4FD7AF24.8080607@zytor.com \
--to=hpa@zytor.com \
--cc=bfalk@gamozolabs.com \
--cc=linux-kernel@vger.kernel.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.