* Double buffer support in Framebuffer?
@ 2011-04-27 23:24 siqiao chen
2011-04-28 3:22 ` Dave Hylands
0 siblings, 1 reply; 3+ messages in thread
From: siqiao chen @ 2011-04-27 23:24 UTC (permalink / raw)
To: kernelnewbies
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?
Thank you!
Philip Chen
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110427/a5f6f13c/attachment.html
^ permalink raw reply [flat|nested] 3+ messages in thread* Double buffer support in Framebuffer?
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
0 siblings, 1 reply; 3+ messages in thread
From: Dave Hylands @ 2011-04-28 3:22 UTC (permalink / raw)
To: kernelnewbies
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Double buffer support in Framebuffer?
2011-04-28 3:22 ` Dave Hylands
@ 2011-04-28 4:47 ` siqiao chen
0 siblings, 0 replies; 3+ messages in thread
From: siqiao chen @ 2011-04-28 4:47 UTC (permalink / raw)
To: kernelnewbies
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2011-04-28 4:47 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).