- 19 Jan, 2009 1 commit
-
-
Austin Yuan authored
Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>
-
- 20 Jan, 2009 1 commit
-
-
chenbinglin authored
-
- 12 Jan, 2009 2 commits
-
-
Austin Yuan authored
Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>
-
Austin Yuan authored
Apply the patch to split va and display/x11 from Gwenole Beauchesne [mailto:gbeauchesne@splitted-desktop.com] Bellow is his explanation: > Finally, looking further at <va_x11.h>, I think it should be enough to have > vaInitialize() in display-dependent headers/libs. The va_x11_getDriverName() > suggestion was to factor out the thing at the implementation (source > code/files) level. > > Or we could keep vaInitialize() in common lib and rather have vaGetDisplay() > in the display-specific part? And, while being at it, also rename the > function to vaCreateDisplay(), to be meaningful about the API change? > > Besides, for a different windowing system, we probably would need more than > just the Display (as we have in X11 land) anyway. e.g. what about OpenGL, > OpenGL E|S? I don't know, it's just an idea. > > I read that Canmore/Sodaville are using the same engines as the Poulsbo > (SGX535 and VXD370). However, the former platforms only support OpenGL E|S. > So, how does video acceleration work here? I know it works, I saw it but > since we still haven't received the machines, I just don't know about the > actual API. You'd probably want libVA there too. > > Splitting libVA between a Core API and a Display API would make it possible > to reduce code duplication from a player point of view. i.e. I don't think > it's necessary to have client applications implement > vaBeginPicture()..vaEndPicture() sequences themselves. I think it should be > the role of the codec library (ffmpeg, in my case), and it should be able to > do so without an explicit dependency on X11. > > On the other hand, the Core API won't be useful/functional alone. So, that > could be confusing too. > > In practise, I would like to have it working as follows. It's my ideal > vision, not necessarily the right/correct one. ;-) > > Roles of a codec implementation library: > - Create buffers > - Render the pictures, in the vaBeginPicture()..vaEndPicture(), > vaRenderPicture() sense > > Roles of a player application: > - Create display, surfaces, and decode pipeline for the codec library > - Render the picture, visually, i.e. in the vaPutSurface() sense > > Example use: > VApplication|initialize display > CodecLibrary|characterise bitstream (codec and other useful info) > VApplication|create decode pipeline > VApplication|create surfaces > CodecLibrary|create buffers (1) > CodecLibrary|render picture (2) > VApplication|display picture (3) > repeat (1) -> (3) while the end of stream is not reached > VApplication|destroy everything > > Have CodecLibrary linked against libva-core-VERSION.so.MAJOR, without any > dependency on windowing system library. > > Have VApplication linked against libva-x11-VERSION.so.MAJOR, itself linked > against libva-core-VERSION.so.MAJOR and other windowing system libraries. > > Regards, > Gwenole. > Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>
-
- 19 Dec, 2008 1 commit
-
-
Austin Yuan authored
Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>
-
- 18 Dec, 2008 1 commit
-
-
Austin Yuan authored
Signed-off-by: Austin Yuan <shengquan.yuan@intel.com>
-
- 20 Nov, 2008 1 commit
-
-
Austin Yuan authored
-
- 22 Oct, 2008 1 commit
-
-
root authored
-
- 29 Aug, 2008 1 commit
-
-
Austin Yuan authored
-
- 09 Jul, 2008 1 commit
-
-
Austin Yuan authored
-
- 02 Jul, 2008 1 commit
-
-
Austin Yuan authored
-
- 01 Jul, 2008 1 commit
-
-
Austin Yuan authored
1. SkipFrame for vaQuerySurfaceStatus 2. disable_deblocking_filter_idc for VAEncSliceParameterBuffer
-
- 14 May, 2008 1 commit
-
-
Austin Yuan authored
-
- 07 May, 2008 1 commit
-
-
Austin Yuan authored
-
- 05 May, 2008 1 commit
-
-
Austin Yuan authored
-
- 29 Apr, 2008 3 commits
-
-
Austin Yuan authored
-
Austin Yuan authored
-
Waldo Bastian authored
-
- 15 Mar, 2008 2 commits
-
-
Waldo Bastian authored
-
Waldo Bastian authored
-
- 14 Mar, 2008 1 commit
-
-
Austin Yuan authored
under rotation mode, but a issue is found that after vaTerminate, XCloseDisplay will meet a SIGSEGV, and debuging shows libXdamage is unloaded from application address space after vaTerminate, and keeping libXdamage all along can workaround this issue. So always link libva with libXdamage here
-
- 13 Mar, 2008 1 commit
-
-
Waldo Bastian authored
-
- 10 Mar, 2008 1 commit
-
-
Waldo Bastian authored
-
- 05 Mar, 2008 1 commit
-
-
Waldo Bastian authored
-
- 20 Feb, 2008 1 commit
-
-
Waldo Bastian authored
-
- 07 Feb, 2008 1 commit
-
-
Waldo Bastian authored
* Bump version to 0.29
-
- 05 Feb, 2008 1 commit
-
-
Waldo Bastian authored
* VC1: reference_distance can have values of 0 - 16 inclusive and needs 5 bits
-
- 07 Dec, 2007 2 commits
-
-
Waldo Bastian authored
-
Waldo Bastian authored
-
- 06 Dec, 2007 2 commits
-
-
Waldo Bastian authored
-
Waldo Bastian authored
-
- 11 Nov, 2007 1 commit
-
-
Waldo Bastian authored
-
- 08 Nov, 2007 1 commit
-
-
Waldo Bastian authored
-
- 07 Nov, 2007 1 commit
-
-
Waldo Bastian authored
- Combine vaCreateBuffer and vaBufferData
-
- 01 Nov, 2007 1 commit
-
-
Waldo Bastian authored
-
- 31 Oct, 2007 1 commit
-
-
Waldo Bastian authored
-
- 29 Oct, 2007 1 commit
-
-
Waldo Bastian authored
-
- 25 Oct, 2007 1 commit
-
-
Waldo Bastian authored
-
- 16 Oct, 2007 1 commit
-
-
Waldo Bastian authored
* Expand mv_mode from 2 to 3 bits
-
- 15 Oct, 2007 1 commit
-
-
Waldo Bastian authored
-