On Tue, Dec 15, 2009 at 12:35 PM, Anthony Liguori <span dir="ltr"><<a href="mailto:anthony@codemonkey.ws">anthony@codemonkey.ws</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">Avi Kivity wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
bochs bios required all 128kB, so this is probably a leftover.<br>
</blockquote>
<br></div></div>
This is apparently well defined in the PIIX spec. There is a bit of a difference between the lower half and upper half of the BIOS region though and I expect this is part of what the problem is. FYI, the following patch works. Surprisingly, we only need to restore the 0xe8000..0xe8fff region. Still trying to understand what's happening.<br>
<br></blockquote><div><br>SeaBIOS is currently using over 64K of space. So, it is extending into the e-segment<br>and thus needs to have the e-segment copied properly (I missed that in my<br>earlier email).<br><br>SeaBIOS is only extending a few K into the e-segment, so only that part needs to<br>
be saved and restored.<br><br>Should SeaBIOS options be trimmed so that it fit under 64K, then the build would<br>create only a 64K rom. However, since it is larger than 64K, it pads itself to 128K. As<br>mentioned before, SeaBIOS can still copy roms into the unused parts of the e-segment,<br>
as it knows which parts of the e-segment it is using.<br><br>-Kevin<br><br></div></div>