Oops, this was my bad.  after looking back at your previous posts, Jörg, I think Ronald is correct.  Which brings me back to an earlier question.  Namely are you loading a zImage or a bzImage?  If you carefully look through the head.S code, you will notice it deciding whether the kernel is loaded high or low.  I believe it does this by checking a value generated at compile time.  Anyway, my understanding is that the big (bzImage) kernels are loaded high 0x101000 and the smaller (zImage) kernels are loaded into low memory  at 0x1000. 

Assuming OpenBIOS puts the processor into protected mode with a 4g address space (a good bet as Ronald has already confirmed this), all you should have to do is jump to the kernel.  If you already have access to the 4g address space while you are loading the kernel from flash this should be the case.

One last question though, did you say you were loading a vmlinux image (uncompressed) into memory?  If so, head.S assumes the image is compressed and trys to uncompress it. 

        Gary

-----Original Message-----
From:   Ronald G. Minnich [SMTP:rminnich@lanl.gov]
Sent:   Tuesday, February 15, 2000 12:56 PM
To:     openbios@elvis.informatik.uni-freiburg.de
Subject:        Re: [OpenBIOS] Starting linux aint much easy ?

I don't think you should fall back into real mode. There's no good reason
to. I think you should look at how LOBOS does its thing, which is to boot
linux entirely in protected mode, and emulate that in your bios.

Falling into real mode is a mess. Also, once you drop to real mode, you
can't address 0x100000 any more. This is probably not what you want, since
your code is at 0x101000.

ron

-
To unsubscribe: send mail to majordomo@freiburg.linux.de
with 'unsubscribe openbios' in the body of the message