From: Gerd Hoffmann <kraxel@redhat.com>
To: Vasilis Liaskovitis <vasilis.liaskovitis@profitbricks.com>
Cc: linux-fbdev@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] add bochs dispi interface framebuffer driver
Date: Fri, 02 Nov 2012 14:14:46 +0100 [thread overview]
Message-ID: <5093C746.50801@redhat.com> (raw)
In-Reply-To: <20121102115346.GB20700@dhcp-192-168-178-175.profitbricks.localdomain>
>> Only with bochsfb or with vesafb (+ fbdev xorg driver) too?
>
> vt-switching with vesafb/X11 works fine on a grml 64-bit image. However, xorg
> uses vesa driver in this case, not fbdev (fbdev / fbdevhw xorg modules are
> initially loaded but then unloaded). X11 uses 1280x768 and vesafb uses 1024x768
> according to dmesg.
You should be able to force the fbdev driver using xorg.conf.
> But i haven't been able to test ubuntu+vesafb. Ubuntu kernels use efifb
> (CONFIG_FB_EFI=y) and fbconsoles don't work at all with this driver +
> qemu/seabios/vgastd.
I think this is a grub2 setup issue. Grub2 can pass gfx mode params to
the linux kernel in a way efifb is able to handle.
> vt7 http://picpaste.de/bochsfb-badstart-AirrXZuF.png
> vt1 http://www.picpaste.de/bochsfb-badstart-f1-EO10MVdF.png
> it still happens with the latest bochsfb driver (tested with 3.6.0 though, not
> 3.7.0-rc3 yet)
Most likely this is a guest-side bug and not specific to bochsfb.
Console switching depends on all parties being cooperative. Nothing
stops an application writing to the framebuffer even it isn't running on
the foreground console.
cheers,
Gerd
prev parent reply other threads:[~2012-11-02 13:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 10:13 [Qemu-devel] [PATCH] add bochs dispi interface framebuffer driver Gerd Hoffmann
2012-10-19 10:35 ` Vasilis Liaskovitis
2012-11-01 13:30 ` Gerd Hoffmann
2012-11-02 11:53 ` Vasilis Liaskovitis
2012-11-02 13:14 ` Gerd Hoffmann [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=5093C746.50801@redhat.com \
--to=kraxel@redhat.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=vasilis.liaskovitis@profitbricks.com \
/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).