public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Mark Meade <mark@lakeshoremicro.com>
To: linux-mtd@lists.infradead.org
Cc: karim@opersys.com
Subject: Re: Avoiding DOC hotplug when Grub fails
Date: Thu, 8 Aug 2002 22:02:07 -0400	[thread overview]
Message-ID: <200208082158.18411.mark@lakeshoremicro.com> (raw)

Karim Yaghmour wrote:

> As far as I can see by browsing this mailing list archive, one
> has to hotplug the DOC device in order to have the HD come up
> first if Grub fails in some way after having hijacked int 19h.
> This is rather inconvenient, to say the least.

I've recently found an easier way - with the M-Sys ISA Eval card, anyway.  I 
assume the PCI card would be similar.

On the ISA card, there is a jumper used to set the DoC Address (C800, D000, 
etc).  If this jumper is removed, the DoC is no longer recognized by the 
BIOS.

If the DoC has int 19h, simply boot without the jumper in place, and then put 
it back after the hard drive boot has finished.  If you have the MTD stuff 
compiled as modules, don't do the modprobe until after the jumper is 
replaced.   Works great, plus eliminates the risky procedure of hotplugging 
the DoC or Eval card.

> Why not just hijack int 16h (keyboard) while we're at it, write
> a small keyboard int handler, and check if the space-bar (or
> some other key) is held down while Grub is booting? If it is,
> then Grub invokes the BIOS's original int 19h which then proceeds
> normally. If it isn't, then Grub continues with its own load
> procedure.

One potential problem is that the low level Grub code that grabs int 19 is 
limited to 512 bytes.  With all the other things that code has to do, there 
might not be enough room to add another int handler.

Mark

             reply	other threads:[~2002-08-09  2:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-09  2:02 Mark Meade [this message]
2002-08-09  2:16 ` Avoiding DOC hotplug when Grub fails Gregg C Levine
2002-08-09  4:01 ` Karim Yaghmour
  -- strict thread matches above, loose matches on Subject: below --
2002-08-09  0:50 Karim Yaghmour

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=200208082158.18411.mark@lakeshoremicro.com \
    --to=mark@lakeshoremicro.com \
    --cc=karim@opersys.com \
    --cc=linux-mtd@lists.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