[Bug 105145] vaExportSurfaceHandle interaction with surface interlaced flag prevents switching on vaapi deinterlacing dynamically

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



changed bug 105145
What Removed Added
Severity major enhancement
Status RESOLVED VERIFIED

Comment # 6 on bug 105145 from
(In reply to k.philipp from comment #5)
> There are some surface hints, but I'm not sure if they fit this use case.

Setting the DISPLAY hint can be used with KMS to display the result without
copying it, so that is not what we are searching for.

But checking the documentation once more VA_SURFACE_ATTRIB_USAGE_HINT_VPP_READ
actually sounds exactly like what we need.

E.g. we switch over to allocate all surfaces in the progressive/frame format
and only use the interlaced/field format when
VA_SURFACE_ATTRIB_USAGE_HINT_VPP_READ is given.

Now you just need to find somebody volunteering to implement that :)

I can assist finding the proper places in the code, but I don't have time to do
it myself.


You are receiving this mail because:
_______________________________________________
dri-devel mailing list
dri-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Index of Archives]     [Linux DRI Users]     [Linux Intel Graphics]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [XFree86]
  Powered by Linux