From: Avi Kivity <avi@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [FYI] Soft feature freeze for 1.0 is 10/15 (three weeks away)
Date: Mon, 26 Sep 2011 20:24:05 +0300 [thread overview]
Message-ID: <4E80B535.1030804@redhat.com> (raw)
In-Reply-To: <CAAu8pHvs7c5+q9-D=kt-QVtY8ip-JoDRQyzZLoXb0nTO2N8=tQ@mail.gmail.com>
On 09/26/2011 08:20 PM, Blue Swirl wrote:
> On Mon, Sep 26, 2011 at 5:18 PM, Avi Kivity<avi@redhat.com> wrote:
> > On 09/26/2011 08:15 PM, Blue Swirl wrote:
> >>
> >> On Mon, Sep 26, 2011 at 10:08 AM, Avi Kivity<avi@redhat.com> wrote:
> >> > On 09/25/2011 08:31 PM, Blue Swirl wrote:
> >> >>
> >> >> >
> >> >> > Please point out a test case and I'll try to fix it.
> >> >>
> >> >> Run qemu-system-ppc without any arguments. There is a black bar
> >> >> (because of vga.chain4), it shouldn't be there.
> >> >
> >> > With your pci hole patch, it's fixed, except for:
> >> >
> >> > escc_mem = escc_init(0x80013000, pic[0x25], pic[0x24],
> >> > serial_hds[0], serial_hds[1], ESCC_CLOCK, 4)
> >> >
> >> > This puts escc bang into the framebuffer. Changing it to 0x90013000
> >> > makes
> >> > the black bar go away.
> >> >
> >> > Before the memory API, this worked, likely because the framebuffer
> >> > overlays
> >> > escc.
> >> >
> >> > The correct fix depends on what the hardware does. Is escc really
> >> > registered into the pci area, and again as a BAR?
> >>
> >> I think the previous code assumed that there is a single BAR with
> >> default address of 0x80013000, but it can move as controlled by macio
> >> mapping.
> >
> > So the fix would be to just drop this extraneous mapping?
>
> The default address is used for early serial printk in OpenBIOS, so it
> should still work.
Ok, so drop the extra mapping, but init the dynamic mapping to 0x80013000.
The whole dual mapping thing is wierd and set up some hoops for me to
jump through, it's probably completely bogus.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2011-09-26 17:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 0:34 [Qemu-devel] [FYI] Soft feature freeze for 1.0 is 10/15 (three weeks away) Anthony Liguori
2011-09-24 8:05 ` Blue Swirl
2011-09-25 14:10 ` Avi Kivity
2011-09-25 16:36 ` Blue Swirl
2011-09-25 16:48 ` Avi Kivity
2011-09-25 17:31 ` Blue Swirl
2011-09-26 10:08 ` Avi Kivity
2011-09-26 10:10 ` Avi Kivity
2011-09-26 17:15 ` Blue Swirl
2011-09-26 17:18 ` Avi Kivity
2011-09-26 17:20 ` Blue Swirl
2011-09-26 17:24 ` Avi Kivity [this message]
2011-09-26 18:07 ` Blue Swirl
2011-09-27 8:33 ` Avi Kivity
2011-09-27 8:57 ` Avi Kivity
2011-09-27 16:39 ` Blue Swirl
2011-09-27 16:44 ` Avi Kivity
2011-09-27 19:19 ` Blue Swirl
2011-09-28 21:21 ` Alexander Graf
2011-09-29 19:28 ` Blue Swirl
2011-09-29 21:19 ` Alexander Graf
2011-09-25 19:50 ` Anthony Liguori
2011-09-30 3:21 ` Stefan Berger
2011-09-30 12:59 ` Anthony Liguori
2011-09-30 14:05 ` Stefan Berger
2011-10-10 12:14 ` Max Filippov
-- strict thread matches above, loose matches on Subject: below --
2011-09-24 21:56 Anthony Liguori
2011-09-25 16:28 ` Blue Swirl
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=4E80B535.1030804@redhat.com \
--to=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).