The 16-bit setup code *has* to run in real mode... that's the only
reason it's 16 bit. As far as the APM BIOS, I'm sure you're aware of
the number of problems caused by APM BIOSes that don't like to be called
the way Linux calls them?
Furthermore, the APM BIOS is called using its 32-bit protected-mode
interface --- which is set up by calling the APM BIOS in real mode in
setup.S; it can't be done while you are in protected mode.
Life isn't that simple, and there's a reason why some of the code that's
in the 16-bit setup code is there, and not after we transition into
32-bit protected mode. After all, if we could move it there, we would;
life is much more pleasant once you're able to leave the 16-bit
universe.
- Ted
-
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/