bcopyxx: when going to 16-bit PM, might as well do it right
authorH. Peter Anvin <hpa@linux.intel.com>
Fri, 17 Apr 2009 00:19:24 +0000 (17:19 -0700)
committerH. Peter Anvin <hpa@linux.intel.com>
Fri, 17 Apr 2009 00:19:24 +0000 (17:19 -0700)
commita7dd6590584c7c243bb256989ebd8f230a86b6ab
tree92ecd1b803128cd78f7bc1730064979e5c580abd
parent2a37f9de661d6bad79c5cc8fb13dbf63a27cf863
bcopyxx: when going to 16-bit PM, might as well do it right

When entering 16-bit PM after shuffle and boot, we might as well
do so sanely.  Specifically, set up the data segments so that they
match the code segment, generating a 16-bit "tiny" model environment.

This makes it a lot saner to bootstrap a proper PM environment from
there if that is what the user intends.  For the presumably more
common case of RM entry, it won't do any harm, and it's only a handful
of additional instructions.

Signed-off-by: H. Peter Anvin <hpa@linux.intel.com>
core/bcopy32.inc
core/bcopyxx.inc
core/com32.inc
doc/comboot.txt