All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 01 Nov 2012 13:30:35 +0000	[thread overview]
Message-ID: <5092797B.5090403@redhat.com> (raw)
In-Reply-To: <20121019103515.GA30341@dhcp-192-168-178-175.profitbricks.localdomain>

On 10/19/12 12:35, Vasilis Liaskovitis wrote:
> Hi,
> 
> On Thu, Mar 08, 2012 at 11:13:46AM +0100, Gerd Hoffmann wrote:
>> This patchs adds a frame buffer driver for (virtual/emulated) vga cards
>> implementing the bochs dispi interface.  Supported hardware are the
>> bochs vga card with vbe extension and the qemu standard vga.
>>
>> The driver uses a fixed depth of 32bpp.  Otherwise it supports the full
>> (but small) feature set of the bochs dispi interface:  Resolution
>> switching and display panning.  It is tweaked to maximize fbcon speed,
>> so you'll get the comfort of the framebuffer console in kvm guests
>> without performance penalty.
> 
> I am testing this driver with qemu-kvm-1.2 or qemu-kvm master (commit)
> and "-std vga". The driver works fine in general.
> 
> When I test a guest that runs X (ubuntu-12.04 desktop amd64), sometimes parts of
> the screen and keyboard input is mixed between the X terminal and fbconsole
> terminals. This happens only on the initial X11 login (right after boot or
> reboot) and only sometimes.

Only with bochsfb or with vesafb (+ fbdev xorg driver) too?

> Xorg driver used is fbdev (i can send xorg log), not sure if another driver
> should be used/implemented for the bochsfb.

Yes, that one is fine.

> CONFIG_FB_BOCHS=m
> CONFIG_FB_VESA=y
> # CONFIG_FB_EFI is not set
> 
> Should FB_VESA be turned to "not set" for this test? (it's not tristate in Kconfig)
> 
> Btw (slightly off-topic) are other framebuffer drivers suitable for the
> standard qemu vga-pci device? Would vesafb or uvesafb work? 

Never tried uvesafb.  vesafb will work too, but run with a fixed
resolution.  bochsfb allows you to change the display resolution at
runtime using fbset.  fbcon is faster too because bochsfb supports
display panning.

Latest version of the patch is here:
  http://www.kraxel.org/cgit/linux/commit/?h=bochsfb

cheers,
  Gerd


WARNING: multiple messages have this Message-ID (diff)
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: Thu, 01 Nov 2012 14:30:35 +0100	[thread overview]
Message-ID: <5092797B.5090403@redhat.com> (raw)
In-Reply-To: <20121019103515.GA30341@dhcp-192-168-178-175.profitbricks.localdomain>

On 10/19/12 12:35, Vasilis Liaskovitis wrote:
> Hi,
> 
> On Thu, Mar 08, 2012 at 11:13:46AM +0100, Gerd Hoffmann wrote:
>> This patchs adds a frame buffer driver for (virtual/emulated) vga cards
>> implementing the bochs dispi interface.  Supported hardware are the
>> bochs vga card with vbe extension and the qemu standard vga.
>>
>> The driver uses a fixed depth of 32bpp.  Otherwise it supports the full
>> (but small) feature set of the bochs dispi interface:  Resolution
>> switching and display panning.  It is tweaked to maximize fbcon speed,
>> so you'll get the comfort of the framebuffer console in kvm guests
>> without performance penalty.
> 
> I am testing this driver with qemu-kvm-1.2 or qemu-kvm master (commit)
> and "-std vga". The driver works fine in general.
> 
> When I test a guest that runs X (ubuntu-12.04 desktop amd64), sometimes parts of
> the screen and keyboard input is mixed between the X terminal and fbconsole
> terminals. This happens only on the initial X11 login (right after boot or
> reboot) and only sometimes.

Only with bochsfb or with vesafb (+ fbdev xorg driver) too?

> Xorg driver used is fbdev (i can send xorg log), not sure if another driver
> should be used/implemented for the bochsfb.

Yes, that one is fine.

> CONFIG_FB_BOCHS=m
> CONFIG_FB_VESA=y
> # CONFIG_FB_EFI is not set
> 
> Should FB_VESA be turned to "not set" for this test? (it's not tristate in Kconfig)
> 
> Btw (slightly off-topic) are other framebuffer drivers suitable for the
> standard qemu vga-pci device? Would vesafb or uvesafb work? 

Never tried uvesafb.  vesafb will work too, but run with a fixed
resolution.  bochsfb allows you to change the display resolution at
runtime using fbset.  fbcon is faster too because bochsfb supports
display panning.

Latest version of the patch is here:
  http://www.kraxel.org/cgit/linux/commit/?h=bochsfb

cheers,
  Gerd

  reply	other threads:[~2012-11-01 13:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-08 10:13 [PATCH] add bochs dispi interface framebuffer driver Gerd Hoffmann
2012-03-08 10:13 ` [Qemu-devel] " Gerd Hoffmann
2012-10-19 10:35 ` Vasilis Liaskovitis
2012-10-19 10:35   ` Vasilis Liaskovitis
2012-11-01 13:30   ` Gerd Hoffmann [this message]
2012-11-01 13:30     ` Gerd Hoffmann
2012-11-02 11:53     ` Vasilis Liaskovitis
2012-11-02 11:53       ` Vasilis Liaskovitis
2012-11-02 13:14       ` Gerd Hoffmann
2012-11-02 13:14         ` Gerd Hoffmann

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=5092797B.5090403@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 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.