On 10/29/2016 04:09 AM, Sean V Kelley wrote:
On Fri, 2016-10-28 at 10:05 +0800, Randy Li wrote:
On 10/27/2016 11:03 PM, Xiang, Haihao wrote:
-----Original Message-----
From: dri-devel [mailto:[email protected]]
On Behalf
Of Randy Li
Sent: Monday, October 24, 2016 3:59 PM
To: [email protected]
Cc: [email protected]; [email protected]
; linux-
[email protected]; Jaquez, VictorX <victorx.jaquez@int
el.com>;
eddie.cai <[email protected]>; 林金发 <[email protected]
om>;
[email protected]; [email protected]
Subject: How to implement a EGL or DRM display in VA-API driver
Hello:
I am going to implement a EGL and DRM display for Rockchip VA-
API driver.
We do have a EGL implementation in Rockchip VA-API driver, but it
is
implemented in the standard way, we did that as a X11 display.
I didn't see the usage of struct VADriverVTableEGL in
gstreamer, and I have
no idea about where should I implement something functions like
eglExportDRMImageMESA().
VADriverVTableEGL is deprecated in libva, we has a more efficient
way to use vaapi and egl.
You can refer to the examples in libyami-utils (https://github.com/
01org/libyami-utils.git) for
how to use vaapi and egl.
I see, thank you.
I looks like the currently VA-API only need vaDeriveImage() and
vaAcquireBufferHandle(), leaving the rendering output buffer to display
to VA-API client. vaapisink from gstreamer would play no role in this?
The DRM seems more complex, the reason I want to use the DRM is
that,
GPU would not work with the 4K video rendering, so the DRM means
that
The guys from algorithm department told me that the main problem is
VA-API can't process video parallelly and it won't process the next
frame until vaEndPicture() and a output function(like vaDeriveImage(),
vaGetImage and vaPutSurface()).
directly output the video into video controller in our platform.
But still have no
idea what kind of thing I should implement in the VA-API driver.
It seems that
the VA-API base library would open a DRM instance for the driver,
but leaving
those configure for connector, encoder, planes to VA-API driver?
About the DRM, I have implemented a version which pretends a X
output, I
would like to know a better way.
Connector properties and their configuration are entirely display port
oriented. "Pretending an X output" is independent of KMS configuration
for your display port.
No, what I do is pretended as a VA_DISPLAY_X11 display. I have read the
examples/grid.cpp from libyami-utils. It seems that those job have been
moved into VA-API client. The whole display system looks like departured.
So the element plugin vaapisink from gstreamer would be drop in the
future? As those job have been done by kmssink and glimagesink.
Sean
configure for connector, encoder, planes aren't a part of va-api
driver. You should check libdrm and drm/i915.
You can refer to the test case of modetest in libdrm
(git.freedesktop.org/git/mesa/drm)
Could you guys give me same sample code or example of those
kind of
display in VA-API or the documents would help(I would not image
there is a
VA-API documents)
--
Randy Li
The third produce department
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
_______________________________________________
dri-devel mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Randy Li
The third produce department
===========================================================================
This email message, including any attachments, is for the sole
use of the intended recipient(s) and may contain confidential and
privileged information. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message. [Fuzhou Rockchip Electronics, INC. China mainland]
===========================================================================
_______________________________________________
Libva mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/libva
