From: ram <ram@curvesoft.com>
To: linux-assembly@vger.kernel.org
Subject: 2 questions on bootsect.S
Date: Sun, 12 Jan 2003 17:24:49 -0500 [thread overview]
Message-ID: <3E21EB31.3080709@curvesoft.com> (raw)
Hi,
I was looking through the linux (2.5.56) arch/i386/boot/bootsect.S and was
puzzled about a couple of things:
1. Near line 221 we have:
sread: .word 0 # sectors read of current track
head: .word 0 # current head
track: .word 0 # current track
However, since a diskette can have at most 2 heads, 80 tracks and 36
sectors
per track, why are these not bytes instead of words especially since
space is
at such a tight premium in this code ?
2. Near line 272 we have "movw $7, %bx" but the documentation I've
been able to find about the "int 0x13" BIOS call says that for service
code 0xe (write character and advance cursor), it does not take an
attribute byte input parameter but rather uses the existing
attribute. Is
this movw instruction superfluous ?
Thanks.
Ram
next reply other threads:[~2003-01-12 22:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-12 22:24 ram [this message]
2003-01-13 21:19 ` 2 questions on bootsect.S Jack Dennon
2003-01-13 21:25 ` Jack Dennon
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=3E21EB31.3080709@curvesoft.com \
--to=ram@curvesoft.com \
--cc=linux-assembly@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 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).