From: Steve Longerbeam <slongerbeam@gmail.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: devel@driverdev.osuosl.org,
Steve Longerbeam <steve_longerbeam@mentor.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/2] staging: vboxvideo: Add page-flip support
Date: Tue, 7 Aug 2018 14:57:06 -0700 [thread overview]
Message-ID: <ac90489b-c4a6-0268-d814-5b979eddd01c@gmail.com> (raw)
In-Reply-To: <20180806083418.GI3008@phenom.ffwll.local>
On 08/06/2018 01:34 AM, Daniel Vetter wrote:
> On Fri, Jul 20, 2018 at 10:17:29AM -0700, Steve Longerbeam wrote:
>> Adds crtc page-flip support by passing the new requested framebuffer
>> to vbox_crtc_do_set_base().
>>
>> There is no attempt to support vblank interrupts, so this page-flip
>> implementation does not try to sync the page-flip to vertical blanking,
>> so expect tearing effects. Is it possible to access the host vblank
>> intervals in VBOX?
> I think it'd be great to move vboxvideo over to atomic instead, which is
> required for destaging anyway, and would give you page flip support for
> free.
Hi Daniel, yes I agree vboxvideo needs to move to the DRM atomic
framework.
Steve
>
>>
>> Steve Longerbeam (2):
>> staging: vboxvideo: Pass a new framebuffer to vbox_crtc_do_set_base
>> staging: vboxvideo: Add page-flip support
>>
>> drivers/staging/vboxvideo/vbox_mode.c | 34 +++++++++++++++++++++++++++++++---
>> 1 file changed, 31 insertions(+), 3 deletions(-)
>>
>> --
>> 2.7.4
>>
>> _______________________________________________
>> dri-devel mailing list
>> dri-devel@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-08-07 21:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 17:17 [PATCH 0/2] staging: vboxvideo: Add page-flip support Steve Longerbeam
2018-07-20 17:17 ` [PATCH 1/2] staging: vboxvideo: Pass a new framebuffer to vbox_crtc_do_set_base Steve Longerbeam
2018-07-20 17:17 ` [PATCH 2/2] staging: vboxvideo: Add page-flip support Steve Longerbeam
2018-08-06 8:34 ` [PATCH 0/2] " Daniel Vetter
2018-08-07 21:57 ` Steve Longerbeam [this message]
2018-08-30 21:48 ` Steve Longerbeam
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=ac90489b-c4a6-0268-d814-5b979eddd01c@gmail.com \
--to=slongerbeam@gmail.com \
--cc=daniel@ffwll.ch \
--cc=devel@driverdev.osuosl.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=steve_longerbeam@mentor.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