Avoiding DOC hotplug when Grub fails

[Gregg C Levine]

Hello from Gregg C Levine
Our correspondent mentions the M-Sys ISA Eval card. I would assume
anyway that the gizmo exists. Can someone also tell me how much this
thing would also cost? I've been attempting to track down a relatively
easy method of evaluating such hardware, and I remembered that most
providers of such hardware also make this cards. If anyone actually has
one that they do not need, plus any blank disks I'd be glad to take it
off their hands.
-------------------
Gregg C Levine hansolofalcon at worldnet.att.net
------------------------------------------------------------
"The Force will be with you...Always." Obi-Wan Kenobi
"Use the Force, Luke."  Obi-Wan Kenobi
(This company dedicates this E-Mail to General Obi-Wan Kenobi )
(This company dedicates this E-Mail to Master Yoda )



> -----Original Message-----
> From: linux-mtd-admin at lists.infradead.org [mailto:linux-mtd-
> admin at lists.infradead.org] On Behalf Of Mark Meade
> Sent: Thursday, August 08, 2002 10:02 PM
> To: linux-mtd at lists.infradead.org
> Cc: karim at opersys.com
> Subject: Re: Avoiding DOC hotplug when Grub fails
> 
> 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
> 
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/