[SeaBIOS] Running out of space in e/f-segments

Avi Kivity avi at redhat.com
Sun Aug 22 19:07:53 CEST 2010

  On 08/22/2010 08:02 PM, Kevin O'Connor wrote:
>>> Even with all its warts I think .code16gcc is the best route.
>> For 16-bit runtime services, I agree.  For POST and 32-bit runtime
>> services, I think we can easily push the code to 4G-2M.
> The 32bit runtime is also tricky, but thankfully it's under 2K of code
> and so it can be left in the f-segment.
> I'm not sure what you mean by "4G-2M" - are you suggesting running XIP
> in the "flash" chip?


> This is possible in qemu/kvm, but it's not
> something you'd want to do on real hardware.  Accesses to the flash
> chip are terribly slow - on real hardware you want to copy the code
> from flash to ram as soon as possible.  (You typically want to
> compress everything in flash also.)

Typically I forget non-qemu constraints, sorry.

I see that ld has some support for overlays, perhaps we can use that?

error compiling committee.c: too many arguments to function

More information about the SeaBIOS mailing list