From: Karim Yaghmour <karim@opersys.com>
To: Mark Meade <mark@lakeshoremicro.com>
Cc: Linux-MTD <linux-mtd@lists.infradead.org>
Subject: Possible fix for Grub hotplug problem [needs testing]
Date: Sat, 10 Aug 2002 17:47:22 -0400 [thread overview]
Message-ID: <3D5589EA.3A9B1082@opersys.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]
I've modified doc_stage1.S to do the following:
o Copy the old interrupt handler (whether it be int 18 or 19) before
overwriting it.
o The Grub int handler calls on the BIOS's int 16 to check whether
the user is holding down the "ctrl" key.
o If he is, then the old handler is copied back in place and invoked.
o If he isn't, then the code continues on with loading the DOC.
I had to shorten the "msgjmp" string to get the code to still fit
in 512 bytes. On a tangential note: given the 512 byte limitations
it may be simpler get rid of any printout and output single chars,
like lilo does when booting. The expensive string ops could then be
left once we're out of the 512 bytes.
I haven't tested the code. Because my real-mode programming skills
are somewhat rusty, I wanted someone else to take a look at it first
in case I made a mistake somewhere. (I would usually test stuff
before sending it off, but hotplugging my card isn't very appealing,
hence the additional caution).
I've attached a bzip2'd copy of my modified doc_stage1.S. The code
I added is surrounded by "#ifdef KEYBRD_READ" statements for easier
reading.
Any comments and suggestions are greatly appreciated.
Karim
===================================================
Karim Yaghmour
karim@opersys.com
Embedded and Real-Time Linux Expert
===================================================
[-- Attachment #2: doc_stage1.S.bz2 --]
[-- Type: application/octet-stream, Size: 4726 bytes --]
reply other threads:[~2002-08-10 21:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3D5589EA.3A9B1082@opersys.com \
--to=karim@opersys.com \
--cc=linux-mtd@lists.infradead.org \
--cc=mark@lakeshoremicro.com \
/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