On Sun, 7 Feb 2016 21:51:23 +0000 Mark Thompson <s...@jkqxz.net> wrote:
> Hi all, > > More VAAPI following. This is only parts one and two (infrastructure), the > other parts have not changed beyond what is needed to support changes to > these two. > > > Changes: > > * Made some more structures user-opaque, added allocation functions for them. > Log classes around them also more consistent. > > * Surface mapping can now explicitly request direct access, and if possible > will get it by default for write-only mapping. > > * Documentation (doxygen) added for all public interfaces. > > * Format handling is improved; the surface configuration can now make RGB > surfaces correctly. (User visibility of RT_FORMAT is removed.) > > > Outstanding: > > * Interaction (or not) with other patches. I asked when the Libav patches are going to land: <wm4> evilril: do you intend to apply the hwctx patches any time soon? <evilril> within a week or two ideally, depending on whether i get any new reviews <evilril> i'm planning to send a new set today or tomorrow > > * There is still no way to get a hardware context through the filter graph. The Libav idea is probably good enough. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
