kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: siqiaochen@gmail.com (siqiao chen)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Double buffer support in Framebuffer?
Date: Wed, 27 Apr 2011 21:47:08 -0700	[thread overview]
Message-ID: <BANLkTikN_XGh2sHEqOqCKv0gjP_WxyipCA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTim32cbFJq_F3G=OSnPMCNyqzTz9rQ@mail.gmail.com>

O, I get it! Thank you for your explanation!


On Wed, Apr 27, 2011 at 8:22 PM, Dave Hylands <dhylands@gmail.com> wrote:

> Hi Philip,
>
> Replying to all this time.
>
> On Wed, Apr 27, 2011 at 4:24 PM, siqiao chen <siqiaochen@gmail.com> wrote:
> > Hello, Could I ask how do I enable double buffer support in FrameBuffer
> > device?
> > I think I could manually increase xres_virtual/yres_virtual to 2 times of
> > the display size in video driver and swap xoffset/yoffset after VSync.
>  But
> > could I know if this is the right way to do double buffering or this
> > function is already built-in?
>
> You're on the right track. You only need to double xres_virtual or
> yres_virtual, not both.
>
> Let's suppose that your display is 800x480. Then your display driver
> needs to size the framebuffer to be 800x960, and you'd use
> FBIOPAN_DISPLAY to toggle between 0,0 and 0,480.
>
> The driver has to support the double sized framebuffer and the pan
> command (or maybe you can modify yoffset directly? I haven't tried
> this approach myself).
>
> --
> Dave Hylands
> Shuswap, BC, Canada
> http://www.davehylands.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110427/22356502/attachment.html 

      reply	other threads:[~2011-04-28  4:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27 23:24 Double buffer support in Framebuffer? siqiao chen
2011-04-28  3:22 ` Dave Hylands
2011-04-28  4:47   ` siqiao chen [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=BANLkTikN_XGh2sHEqOqCKv0gjP_WxyipCA@mail.gmail.com \
    --to=siqiaochen@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).