Re: booting the kernel when ia32 processor is already in protected mode

Richard B. Johnson (root@chaos.analogic.com)
Fri, 20 Aug 1999 11:27:47 -0400 (EDT)


On Fri, 20 Aug 1999, Keith Owens wrote:

> On Thu, 19 Aug 1999 22:27:10 -0700,
> Lincoln Dale <ltd@interlink.com.au> wrote:
> >i've got a computer that has (already built-in) an impressive bootstrap-loader.
> >it can load an image from disk, network (rcp, ftp, tftp) or from flash.
> >
> >it can load a Linux kernel (provided it is a raw ELF file, such as that
> >normally kept in arch/i386/boot/compress/bvmlinux), and execute at the
> >appropriate place (0x100000).
> >
> >unfortunately, the processor is already in protected-mode by the time the
> >linux kernel starts running. this is where things 'stop'.
>

Look at the boot code. It puts the machine into protected mode before it
jumps to the image at 1 megabyte. It had to do this because the real-mode
16-element segments can only reach to just under 1 megabyte.

So the fact that you are in protected mode probably has nothing to do with
the 'stop'. Instead, note that the boot code reprograms the interrupt
controller. If you try to execute the raw image at 1 megabyte, without
first reprogramming the controller and masking off the interrupts, all
bets are off.

Cheers,
Dick Johnson
**** FILE SYSTEM WAS MODIFIED ****
Penguin : Linux version 2.3.13 on an i686 machine (400.59 BogoMips).
Warning : It's hard to remain at the trailing edge of technology.

-
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/