> > printk. No way to get a message out without detecting the problem in
> > the real mode boot loader and using BIOS I/O.
>
> Knowing this I'd suggest that the few files that are needed to get the
> message out are compiled using the standard Pentium-instructions.
>
> The CPU generates an unimplemented instruction trap, right? Would it
> be doable to write a quick and dirty handler for that trap? (That's
> the method I used to get Xinu up and running on the LSI03).
Much better to do the checks in the short piece of 16bit boot code we have.
For that matter we have a perfectly usable 16bit C compiler if we want to
get more complex 8)
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jul 15 2000 - 21:00:10 EST