Hi All,
We are having some problem regarding gstreamer Vaapi Plugin would like to discuss.
We are using gstreamer0.10.36 for our 1080p mp4 playback and we have used following gstraemer pipeline.
filesrc- decodebin-queue-ffmpegcolorspace-xvimagesink
Here we are facing lot of buffer drop
Hi Meena,
On Thu, Mar 27, 2014 at 06:58:53AM +, Meenakumari Shedole wrote:
Hi All,
We are having some problem regarding gstreamer Vaapi Plugin would like to
discuss.
We are using gstreamer0.10.36 for our 1080p mp4 playback and we have used
following gstraemer pipeline.
filesrc-
On 2014-03-25 15:31, David Nyström wrote:
On 2014-03-24 17:00, Richard Purdie wrote:
As development on 1.6 finishes up, its time to think about what we
should be doing in the 1.7 cycle.
I think from my perspective, in 1.7 I'd like to see us looking at
Developer Workflow. Its a generic topic
On 27 March 2014 05:50, Stuart Longland stua...@vrt.com.au wrote:
The terminal reports itself as TERM=xterm. When I do a `cat`, I observe
that matchbox-terminal is reporting F1-F5 using VT100 terminal
sequences, but F6-F10 using VT220 sequences. If I set TERM=vt100, I get
F1-F5 working, but
On 26 March 2014 22:12, Burton, Ross ross.bur...@intel.com wrote:
On 26 March 2014 22:04, Khem Raj raj.k...@gmail.com wrote:
There were interest in other threads in having musl as an alternative
to eglibc/uclibc that we already have in OE, in that direction I have
poured in my on and off work
On 27 March 2014 06:58, Meenakumari Shedole meenakumar...@hcl.com wrote:
filesrc- decodebin-queue-ffmpegcolorspace-xvimagesink
Try just using playbin2 instead of constructing a pipeline manually,
there's lot of smarts that you'll need to do manually otherwise.
Ross
--
We can't use RunSanityTests as it is because the default
test suites (which are defined in testimage.bbclass) include rpm and smart.
Anything included in TEST_SUITES is a mandatory test and will be a fail in this
buildset as obviously this images don't have rpm/smart.
Also we can't use 'ping auto'
Excellent information! Thanks for all the workflow examples, this is great.
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
The build tests for iptables/cvs/sudoku take too much time on qemumips
and usually buildbot ends up killing the step as it hits the timeout,
so we should drop them.
Signed-off-by: Stefan Stanacar stefanx.stana...@intel.com
---
buildset-config.master/nightly-qa-targetbuilds.conf | 3 ---
1 file
Hi Ross,
On 27/03/14 22:27, Burton, Ross wrote:
Can you paste the output of cat to confirm the values you're seeing?
The xterm guide says VT100 for F1-F4 (as VT100 doesn't define F5
onwards) and VT220 for F5-F10 and that's what I'm seeing when I
attempt this (F10 specifically being ^[[21~).
On 28/03/14 05:57, Stuart Longland wrote:
Hi Ross,
On 27/03/14 22:27, Burton, Ross wrote:
Can you paste the output of cat to confirm the values you're seeing?
The xterm guide says VT100 for F1-F4 (as VT100 doesn't define F5
onwards) and VT220 for F5-F10 and that's what I'm seeing when I
Hi Beth,
于 2014年03月27日 05:30, Flanagan, Elizabeth 写道:
A list of exactly what files you use for QA would be grand.
We can use http://autobuilder.yoctoproject.org/pub/nightly/20140326-1/
as our base.
We don't use all qemu-lsb , beagleboard-lsb, routerstationpro-lsb, and
p1022ds-lsb
12 matches
Mail list logo
