linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Koala GNU <koala.gnu@tiscalinet.it>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: froom assembly to C in boot code
Date: Fri, 25 Jul 2003 20:05:08 +0200	[thread overview]
Message-ID: <3F217154.30004@tiscalinet.it> (raw)

[-- Attachment #1: Type: text/plain, Size: 1181 bytes --]

Hi all,

I forward to the lkml a mail I posted on kernelnewbies hoping someone of 
you can help me.
-------------------------------------------------------------------------------------------------------------------------

Hi,

for a couple of weeks I worked on some examples about boot process. In 
my previous post on kernelnewbies I post some of them.

Now I have a problem. My goal is to boot from a diskette, load the setup 
code (4 sectors), load the kernel at 0x10000 and move it at 0x1000 
trying to execute a main C routine that
should represent the start of the kernel. This C routine print simply 
"Hello Kernel".

For my job I used the examples of Berlin Brown at 
http://bama.ua.edu/~brown084/main.html  because this code is a 
simplified version of the linux boot process.

Attached there is my code, hoping someone of you can give a look at it 
and tell me if there is something wrong (I think so).

Before the jump to 0x0100 all seems work fine. The problem happen when I switch in 
protected mode and try to jump to 0x0100.

Ahhhh!!! I use bochs for my test.


PS

To build my code type:

make clean (when necessary)
make all

to write on a diskette:
make disk




[-- Attachment #2: boot.tar.gz --]
[-- Type: application/x-gzip, Size: 40960 bytes --]

             reply	other threads:[~2003-07-25 17:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-25 18:05 Koala GNU [this message]
2003-07-25 22:35 ` Gianni Tedesco

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=3F217154.30004@tiscalinet.it \
    --to=koala.gnu@tiscalinet.it \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: froom assembly to C in boot code' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).