From: "Riley Williams" <Riley@Williams.Name>
To: <koala.gnu@tiscalinet.it>
Cc: <Linux-Kernel@Vger.kernel.org>
Subject: RE: Linux boot code
Date: Mon, 14 Jul 2003 17:15:08 +0100 [thread overview]
Message-ID: <BKEGKPICNAKILKJKMHCACEAKEOAA.Riley@Williams.Name> (raw)
In-Reply-To: <3F12AC57.2080609@tiscalinet.it>
Hi.
> I am looking at the boot code in bootsect.S and I have some doubt.
> I tried to search the answers to my questions on
> marc.theaimsgroup.com and on Google but I haven't found them.
I know nothing about the former site, so can't comment thereon.
> Probably these are newbie question but I'll appreciate if someone
> of you help me.
I'll do what I can.
> 1) In the bootsect code the first thing that is done is to copy
> the boot sector to 0x90000 and move the program count to
> 0x9000, go. Why it is necessary move the code there? Is it not
> possible continue the process from 0x7C00?
Following moving the boot code there, the next step is to load the
kernel image, either from 0x10000 (64k) or from 1M upwards, this
being dependent on various factors. However, the boot sector holds
several flags whose values are important AFTER the kernel image has
been loaded, so is moved out the way first.
> 2) Another step is to move the parameters table from 0x78:0 to
> 0x9000:0x4000-12. What are the info contained in this table?
> Can you send me a link to a site that specify these info?
> Without these info I am not able to understand these three
> line of code
>
> movb $36, 0x4(%di) # patch sector count
> movw %di, %fs:(%bx)
> movw %es, %fs:2(%bx)
That area of memory contains parameters configured by the BIOS of
the machine in question. I would suspect it's the parameters for
the floppy drives, and the code that follows is presumably that
used to determine how many sectors per track the floppy in /dev/fd0
actually has.
> Thanks in advance for your help
No problem.
Best wishes from Riley.
---
* Nothing as pretty as a smile, nothing as ugly as a frown.
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.500 / Virus Database: 298 - Release Date: 10-Jul-2003
next parent reply other threads:[~2003-07-14 16:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3F12AC57.2080609@tiscalinet.it>
2003-07-14 16:15 ` Riley Williams [this message]
2003-07-15 9:17 ` Linux boot code Koala GNU
2003-07-15 16:03 ` Randy.Dunlap
2003-07-15 18:01 ` Hua Zhong
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=BKEGKPICNAKILKJKMHCACEAKEOAA.Riley@Williams.Name \
--to=riley@williams.name \
--cc=Linux-Kernel@Vger.kernel.org \
--cc=koala.gnu@tiscalinet.it \
/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 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).