[SeaBIOS] [PATCH] don't produce overly large images

Jan Beulich JBeulich at suse.com
Wed Aug 28 15:41:38 CEST 2013


>>> On 28.08.13 at 14:54, Kevin O'Connor <kevin at koconnor.net> wrote:
> On Wed, Aug 28, 2013 at 12:38:57PM +0100, Jan Beulich wrote:
>> >>> On 28.08.13 at 13:10, Gerd Hoffmann <kraxel at redhat.com> wrote:
>> > And your patch fixes the mentioned runtime failure?  Previous message
>> > sounded like the patch was purely cosmetic ...
>> 
>> No, the fix for the runtime failure was a different one (outside
>> of SeaBIOS itself). It just confused me in the process of finding
>> the root cause that the image consumed the whole 256k of ROM
>> space for no good reason.
> 
> That is not correct.  There is a reason for the rom to be 256K - old
> versions of QEMU did not support 192K and the configured SeaBIOS code
> required more than 128K.  The 256K is not consumed by SeaBIOS - the
> first thing SeaBIOS does is turn the area into memory, relocate most
> of its code out of the area, and then open up the space for option
> roms, internal ram storage, and UMBs.

Yeah, I wasn't precise enough in my statement - I should have
added "initially".

Jan




More information about the SeaBIOS mailing list