For gstreamer-vaapi and libva, if it's really hard to use same one for both profiles, we can fork. At least in initial stage we can fork to make things move forward.
Anyway, it shouldn't block us we use same gstreamer 1.X (core and most of other good/base/bad/ugly/libav plugins )for both mobile and IVI. Thanks, Peter From: [email protected] [mailto:[email protected]] On Behalf Of Yuan, Feng Sent: Wednesday, October 09, 2013 10:27 AM To: Yin, Yan; [email protected] Subject: Re: [Dev] Clarificaiton: gstreamer git paths and branches in tizen.org Hi, Looks like IVI and mobile would merge into one same branch for all gst-xxx packages on Tizen 3.0. Something about gstreamer-vaapi in my mind. 1. Rotation. Tizen phone has specific rotation which doesn't used in upstream. And IVI doesn't need rotation. Though upstream code has rotation feature, but it doesn't work. 2. Libva dependency. IVI based on GEN platform and used latest libva version. Phone based on PVR and used a very old libva version. Decoder should be same the different libva version. But encoder APIs changed lots. This would make phone to make hard decisions to choose, Option 1, change to latest libva version, but driver need lots changes. Lots unstable issues there. Option 2, make gstreamer-vaapi works for both libva versions, starts another porting works there. No matter which option to choose, gst-vaapi also need to consider another issue, the same code should work both on PVR and GEN. Drivers have different requirement even on the same libva APIs. 3. IVI may also have specific fixes and phone doesn't need. e.g, IVI doesn't support MEPG4/H.263 decoder but phone need to have. Maybe these things are easier to fix or harder than I think. Thanks, Wind From: Yin, Yan Sent: Tuesday, October 08, 2013 6:01 PM To: [email protected]<mailto:[email protected]> Cc: Zhao, Halley; Yuan, Feng; Lynch, Rusty; [email protected]<mailto:[email protected]> Subject: Clarificaiton: gstreamer git paths and branches in tizen.org Hi, The git paths and branches of gstreamer (and gst-plugins-xxx) are somewhat confusing in tizen.org due to many historical reasons, and here comes a clarification, hopefully it can address some of your confusions. let's take gst-plugins-base for example, the same rule applies to gstreamer/gst-plugins-base/gst-plugins-good/gst-plugins-bad/gst-plugins-ugly/gst-libav/gst-omx/gstreamer-vaapi. Git path Git Branches Implications framework/multimedia/gst-plugins-base0.10 1.0_post 2.0alpha master tizen_2.0 tizen_2.1 tizen_2.2 l This git path is used for Tizen 2.x only. l For Tizen 3.0 development, this git path won't be used. platform/upstream/gst-plugins-base devel pristine-tar tizen tizen_2.1_compat upstream l This git path is used for Tizen 3.x and future, for both IVI and Mobile profile. l The "tizen_2.1_compat" branch hosts the 0.10.x API version code base from tizen 2.x, while "tizen" branch hosts the 1.x API version code base targeting for tizen 3.x. l The "tizen_2.1_compat" branch will generate package with 0.10 suffix in package name, while "tizen" branch will generate package without any suffix, they can co-exist in same OBS project and one image. l The "tizen_2.1_compat" branch might be renamed to "tizen_2.x_compat" soon. profile/ivi/gst-plugins-base 1.0 2.0 2.0alpha 2.0alpha-wayland l This git path is used for Tizen 2.x IVI profile only. l For Tizen 3.0 development, this git path won't be used. profile/mobile/gst-plugins-base0.10 Tizen l This git path would be deleted soon. Regards, Yan
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
