From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
Avi Kivity <avi@redhat.com>,
Anthony Liguori <anthony@codemonkey.ws>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Cirrus bugs vs endian: how two bugs cancel each other out
Date: Tue, 07 Aug 2012 07:13:50 +1000 [thread overview]
Message-ID: <1344287630.24037.106.camel@pasglop> (raw)
In-Reply-To: <501FCE5F.4090909@redhat.com>
On Mon, 2012-08-06 at 16:02 +0200, Gerd Hoffmann wrote:
>
> A vbe rom isn't a big deal. You probably want support the 0x01CE and
> 0x01CF ports (on x86) so the vgabios running in real mode can easily
> reach the bochs interface registers without a protected mode round
> trip
> for mmio access.
>
> I *think* for seavgabios this needs just a rebuild with an approximate
> configuration (see roms/Makefile and roms/config.vga.*). The code
> already checks whenever bar 0 is actually memory not mmio because this
> is needed for the vmware vga too.
My current layout is
BAR 0 : virtio (including commands to access all the registers)
BAR 1 : MMIO regs (there just in case, they might come in handy
to make the DRM driver more oops-resistant,
but they are unused by my WIP code)
BAR 2 : framebuffer for scanout
I have legacy VGA & Bochs VBE ports wired up as well (it's trivial), did
a quick vgabios change and that works, I haven't looked at seabios yet
but it looks trivial enough.
I have a port of SLOF that uses the virtio channel to configure the
linear mode (using the VBE regs via the virtio tunnel) and that works.
I've started putting together a DRM +fb driver for the guest side, but
that's not done yet.
I've also done a trivial 2D blitter mostly for use by the fb and/or SLOF
but I haven't wired it up yet.
Cheers,
Ben.
next prev parent reply other threads:[~2012-08-06 21:13 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-30 6:24 [Qemu-devel] Cirrus bugs vs endian: how two bugs cancel each other out Benjamin Herrenschmidt
2012-07-30 10:08 ` Avi Kivity
2012-07-30 11:20 ` Benjamin Herrenschmidt
2012-07-30 11:25 ` Avi Kivity
2012-07-30 11:54 ` Benjamin Herrenschmidt
2012-07-30 11:58 ` Avi Kivity
2012-07-30 12:08 ` Benjamin Herrenschmidt
2012-07-30 12:15 ` Avi Kivity
2012-07-30 12:23 ` Benjamin Herrenschmidt
2012-07-30 16:24 ` Alon Levy
2012-07-30 20:19 ` Anthony Liguori
2012-07-30 22:24 ` Benjamin Herrenschmidt
2012-07-31 8:10 ` Alon Levy
2012-08-01 14:35 ` Avi Kivity
2012-08-06 12:57 ` Gerd Hoffmann
2012-07-30 13:18 ` Anthony Liguori
2012-07-30 13:30 ` Avi Kivity
2012-07-30 13:45 ` Anthony Liguori
2012-07-30 13:55 ` Avi Kivity
2012-07-30 14:29 ` Anthony Liguori
2012-07-30 14:36 ` Avi Kivity
2012-07-30 16:01 ` Anthony Liguori
2012-07-30 23:47 ` Rusty Russell
2012-07-31 3:16 ` Benjamin Herrenschmidt
2012-08-06 14:02 ` Gerd Hoffmann
2012-08-06 21:13 ` Benjamin Herrenschmidt [this message]
2012-08-01 23:29 ` Andreas Färber
2012-08-06 13:47 ` Gerd Hoffmann
2012-08-06 14:35 ` Anthony Liguori
2012-07-31 8:20 ` Alon Levy
2012-07-30 22:15 ` Benjamin Herrenschmidt
2012-07-31 0:17 ` Anthony Liguori
2012-07-31 3:26 ` Benjamin Herrenschmidt
2012-08-06 13:20 ` Gerd Hoffmann
2012-08-06 21:16 ` Benjamin Herrenschmidt
2012-08-07 5:30 ` Gerd Hoffmann
2012-08-07 6:07 ` Benjamin Herrenschmidt
2012-07-30 16:19 ` Alon Levy
2012-08-01 15:42 ` Andreas Färber
2012-08-01 19:22 ` Anthony Liguori
2012-08-03 6:45 ` Alon Levy
2012-08-03 13:41 ` Anthony Liguori
2012-08-07 7:00 ` Alon Levy
2012-08-07 8:01 ` Gerd Hoffmann
2012-08-07 13:05 ` Erlon Cruz
2012-08-07 14:07 ` Gerd Hoffmann
2012-08-07 19:43 ` Erlon Cruz
2012-08-08 6:18 ` Gerd Hoffmann
2012-08-08 14:14 ` Erlon Cruz
2012-08-09 6:17 ` Gerd Hoffmann
2012-07-30 15:18 ` Blue Swirl
2012-07-30 15:30 ` Peter Maydell
2012-07-30 15:44 ` Blue Swirl
2012-07-31 8:44 ` ronnie sahlberg
2012-07-31 10:30 ` Benjamin Herrenschmidt
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=1344287630.24037.106.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rusty@rustcorp.com.au \
/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.