From: Jason Baron <jbaron@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: seabios@seabios.org, qemu-devel@nongnu.org, mst@redhat.com
Subject: Re: [Qemu-devel] [PATCH] seabios: correct setting of datalow_base for large rom images
Date: Thu, 7 Jun 2012 09:46:43 -0400 [thread overview]
Message-ID: <20120607134643.GA12564@redhat.com> (raw)
In-Reply-To: <20120606000921.GA32725@morn.localdomain>
On Tue, Jun 05, 2012 at 08:09:21PM -0400, Kevin O'Connor wrote:
> On Tue, Jun 05, 2012 at 12:09:18PM -0400, Jason Baron wrote:
> > I've been creating 256kb rom images with larger acpi tables for second level
> > buses. After a recent re-base, my rom images no longer built. Bisected to:
> >
> > commit 46b82624c95b951e8825fab117d9352faeae0ec8
> > Author: Kevin O'Connor <kevin@koconnor.net>
> > Date: Sun May 13 12:10:30 2012 -0400
> >
> > Add mechanism to declare variables as "low mem" and use for extra stack.
> >
> >
> > Where sec32low_top is greater than datalow_base. Currently, datalow_base is
> > calculated by subtracting a 64kb offset. Updating it to 128kb, resolved this
> > issue for me, while still continuing to create smaller rom images as expected.
>
> Thanks. The problem causing the build to fail is that negative
> numbers aren't encoded properly. That's easy to fix, but it quickly
> uncovers a problem with relocations. Some of the 16bit code has 16bit
> relocations and those wont be handled right if the integer wraps. I
> put together a fix (see below) but it's a bit ugly.
>
ok, yes I can confirm that the patch fixes this issue for me.
Thanks,
-Jason
prev parent reply other threads:[~2012-06-07 13:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 16:09 [Qemu-devel] [PATCH] seabios: correct setting of datalow_base for large rom images Jason Baron
2012-06-06 0:09 ` Kevin O'Connor
2012-06-07 13:46 ` Jason Baron [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120607134643.GA12564@redhat.com \
--to=jbaron@redhat.com \
--cc=kevin@koconnor.net \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.