qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: qemu-devel@nongnu.org
Cc: Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH] [RFC] Variable video ram size option
Date: Thu, 15 Jan 2009 16:23:47 +0000	[thread overview]
Message-ID: <20090115162347.GA5440@shareable.org> (raw)
In-Reply-To: <5E237914-B830-420A-99BE-4C1959DDFC66@exactcode.de>

Rene Rebe wrote:
> >I think the Linux "vesafb" driver uses all available VRAM for
> >scrolling in draws-text-on-graphic-framebuffer mode.
> 
> But only with ypan enabled, which wasn't the default when I took a  
> look the last time.

That's right.

I don't know why "ypan" is off by default; it's hard to imagine it not
working on anything vaguely VBE-like, or even VESA (pre-VBE), since a
lot of DOS games need the panning feature to work for double/triple
buffering.

If you're using Linux guest with VESA framebuffer console, rather than
a text-mode console, I'd recommend kernel boot option "video=vesafb:ypan",
to save considerable CPU when scrolling the console.

I don't know if "video=vesafb:ywrap" works on the QEMU VBE emulation.
That'd be better.

-- Jamie





>  -- René Rebe - ExactCODE GmbH - Europe, Germany, Berlin
> http://exactcode.de | http://t2-project.org | http://rene.rebe.name

  reply	other threads:[~2009-01-15 16:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-12 19:13 [Qemu-devel] [PATCH] [RFC] Variable video ram size option Trolle Selander
2009-01-14 20:07 ` Paul Brook
2009-01-14 20:41   ` Trolle Selander
2009-01-14 21:30     ` Paul Brook
2009-01-14 22:47       ` Trolle Selander
2009-01-15 13:08         ` Jamie Lokier
2009-01-15 15:37           ` Rene Rebe
2009-01-15 16:23             ` Jamie Lokier [this message]
2009-01-15 17:36               ` Gerd Hoffmann
2009-01-15 20:57                 ` Jamie Lokier
2009-01-15 21:41                   ` Gerd Hoffmann
  -- strict thread matches above, loose matches on Subject: below --
2009-01-09 19:45 Trolle Selander
2009-01-10  0:02 ` Paul Brook
2009-01-10  1:26   ` Trolle Selander
2009-01-10  6:45     ` Blue Swirl
     [not found]   ` <4967E7D7.4040605@eu.citrix.com>
     [not found]     ` <200901091716.00827.paul@codesourcery.com>
2009-01-10  1:27       ` Trolle Selander
     [not found]       ` <4967ECA7.6040809@eu.citrix.com>
     [not found]         ` <200901091747.06462.paul@codesourcery.com>
2009-01-10  1:28           ` Trolle Selander
2009-01-10  1:47             ` Jamie Lokier
2009-01-11  7:53 ` Avi Kivity
2009-01-12 17:43   ` Trolle Selander

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=20090115162347.GA5440@shareable.org \
    --to=jamie@shareable.org \
    --cc=paul@codesourcery.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).