public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: cvs-notify@infradead.org
Subject: MTD CVS update: 'mtd/grub doc_stage1.S'
Date: Thu, 01 Jun 2000 01:49:18 +0100	[thread overview]
Message-ID: <E12xJAk-0004T1-00@infradead.org> (raw)

Update of /home/cvs/mtd/grub
In directory infradead.org:/tmp/cvs-serv17114

Modified Files:
	doc_stage1.S 
Log Message:
Fix the setup of the INT 19h handler so we are no longer using the
previously initialised %es register as the segment address of the vector.

Also fix the segment registers in the actual copy, so that we put the 
right stuff in place, rather than starting our copy at 0000:0000.

I can hardly believe that this has ever worked. It seems that by an
amazing coincidence, the IPL ROM sets %es to 0x2000 before jumping to
the code - so even though we were using an uninitialised segment
address pointer, and our copy of the IRQ handler to the _intended_
location went AWOL, we ended up with the INT 19h handler pointing at
the location in memory at which the IPL ROM loads the SPL, before the
SPL relocates itself into the reserved area.

So as long as nothing touched that memory later in the startup sequence,
it would still be there when the BIOS got round to calling INT 19h to
boot. This is why it worked on simple machines like my 386 testbed, but
nothing else.

I hereby declare myself to be Today's Official Mr F*** All Good.



To unsubscribe, send "unsubscribe mtd" to majordomo@infradead.org

             reply	other threads:[~2000-06-01  0:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-01  0:49 David Woodhouse [this message]
2000-06-01  1:00 ` MTD CVS update: 'mtd/grub doc_stage1.S' David Woodhouse
  -- strict thread matches above, loose matches on Subject: below --
2000-05-05 12:12 David Woodhouse

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=E12xJAk-0004T1-00@infradead.org \
    --to=dwmw2@infradead.org \
    --cc=cvs-notify@infradead.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