From: Joshua Lock

Sent: Wednesday, October 20, 2010 8:05 AM

On Tue, 2010-10-19 at 14:31 -0700, Saul Wold wrote:

Dongxiao,

Can you take a look at this since you have worked with the

I did a sloppy job pushing my changes when leaving the office but

I have replicated most/all of the in the josh/demo branch.

I also took a look through the rygel code to see what gstreamer

are explicitly being used, I've created a list and tried to ensure as
many as possible of them are in the IMAGE_INSTALL list for
poky-image-rygel, adding them to the RDEPENDS for rygel doesn't

to have included them in the image I just created...

Full list of names of pipeline elements I found in the rygel code
follows:

decodebin2, videorate, videoscale, ffmpegcolorspace, ffenc_wmv1,
twolame, lame, mp3parse, ffenc_wmav2, convert-sink-pad,
ffenc_mpeg2video, audio-src-pad, audio-sink-pad, audio-enc-sink-pad,
sink, mpegtsmux, audioconvert, audioresample, audiorate, capsfilter,
audiotestsrc, videotestsrc, ffmux_asf

Have all of above elements already enabled in your branch, or is it

in progress to follow up?

Is it a separate issue from segfault or related in your gut-feeling?

On Wed, 2010-10-20 at 01:04 +0100, Joshua Lock wrote:

On Tue, 2010-10-19 at 14:31 -0700, Saul Wold wrote:

Dongxiao,

Can you take a look at this since you have worked with the gstreamer?

I did a sloppy job pushing my changes when leaving the office but think
I have replicated most/all of the in the josh/demo branch.

I also took a look through the rygel code to see what gstreamer elements
are explicitly being used, I've created a list and tried to ensure as
many as possible of them are in the IMAGE_INSTALL list for
poky-image-rygel, adding them to the RDEPENDS for rygel doesn't appear
to have included them in the image I just created...

Full list of names of pipeline elements I found in the rygel code
follows:

decodebin2, videorate, videoscale, ffmpegcolorspace, ffenc_wmv1,
twolame, lame, mp3parse, ffenc_wmav2, convert-sink-pad,
ffenc_mpeg2video, audio-src-pad, audio-sink-pad, audio-enc-sink-pad,
sink, mpegtsmux, audioconvert, audioresample, audiorate, capsfilter,
audiotestsrc, videotestsrc, ffmux_asf

The image I just built with my latest changes in josh/demo worked!?!
Rygel did not segfault :-)

If you have time Dongxiao (or anyone else) I'd appreciate if you could
double-check my changes (my install_append in rygel to create a .config
isn't working, so you'll need to do that manually and run
rygel-preferences to disable the tracker plugin).
If you could test using Rygel as a renderer for some content served by
the mediatomb image, that would be much appreciated. You'll want
gupnp-av-cp as provided by gupnp-tools to control the renderer and
content server.

From: Darren Hart
Sent: Wednesday, October 20, 2010 8:24 AM

On 10/19/2010 05:16 PM, Joshua Lock wrote:

On Wed, 2010-10-20 at 01:04 +0100, Joshua Lock wrote:

On Tue, 2010-10-19 at 14:31 -0700, Saul Wold wrote:

Dongxiao,

Can you take a look at this since you have worked with the gstreamer?

I did a sloppy job pushing my changes when leaving the office but think
I have replicated most/all of the in the josh/demo branch.

I also took a look through the rygel code to see what gstreamer elements
are explicitly being used, I've created a list and tried to ensure as
many as possible of them are in the IMAGE_INSTALL list for
poky-image-rygel, adding them to the RDEPENDS for rygel doesn't appear
to have included them in the image I just created...

Full list of names of pipeline elements I found in the rygel code
follows:

decodebin2, videorate, videoscale, ffmpegcolorspace, ffenc_wmv1,
twolame, lame, mp3parse, ffenc_wmav2, convert-sink-pad,
ffenc_mpeg2video, audio-src-pad, audio-sink-pad, audio-enc-sink-pad,
sink, mpegtsmux, audioconvert, audioresample, audiorate, capsfilter,
audiotestsrc, videotestsrc, ffmux_asf

The image I just built with my latest changes in josh/demo worked!?!
Rygel did not segfault :-)

If you have time Dongxiao (or anyone else) I'd appreciate if you could
double-check my changes (my install_append in rygel to create a .config
isn't working, so you'll need to do that manually and run
rygel-preferences to disable the tracker plugin).
If you could test using Rygel as a renderer for some content served by
the mediatomb image, that would be much appreciated. You'll want
gupnp-av-cp as provided by gupnp-tools to control the renderer and
content server.

It is my udnerstanding that we plan to run both the renderer and the
gupnp-av-cp on each "player". That is an ARM BeagleBoard and a PowerPC
*unknown* board. Each will have a suitable display. Is this your
understanding/intention?

From: Tian, Kevin
Sent: Wednesday, October 20, 2010 8:31 AM

From: Darren Hart
Sent: Wednesday, October 20, 2010 8:24 AM

On 10/19/2010 05:16 PM, Joshua Lock wrote:

On Wed, 2010-10-20 at 01:04 +0100, Joshua Lock wrote:

On Tue, 2010-10-19 at 14:31 -0700, Saul Wold wrote:

Dongxiao,

Can you take a look at this since you have worked with the gstreamer?

I did a sloppy job pushing my changes when leaving the office but think
I have replicated most/all of the in the josh/demo branch.

I also took a look through the rygel code to see what gstreamer elements
are explicitly being used, I've created a list and tried to ensure as
many as possible of them are in the IMAGE_INSTALL list for
poky-image-rygel, adding them to the RDEPENDS for rygel doesn't appear
to have included them in the image I just created...

Full list of names of pipeline elements I found in the rygel code
follows:

decodebin2, videorate, videoscale, ffmpegcolorspace, ffenc_wmv1,
twolame, lame, mp3parse, ffenc_wmav2, convert-sink-pad,
ffenc_mpeg2video, audio-src-pad, audio-sink-pad, audio-enc-sink-pad,
sink, mpegtsmux, audioconvert, audioresample, audiorate, capsfilter,
audiotestsrc, videotestsrc, ffmux_asf

The image I just built with my latest changes in josh/demo worked!?!
Rygel did not segfault :-)

If you have time Dongxiao (or anyone else) I'd appreciate if you could
double-check my changes (my install_append in rygel to create a .config
isn't working, so you'll need to do that manually and run
rygel-preferences to disable the tracker plugin).
If you could test using Rygel as a renderer for some content served by
the mediatomb image, that would be much appreciated. You'll want
gupnp-av-cp as provided by gupnp-tools to control the renderer and
content server.

It is my udnerstanding that we plan to run both the renderer and the
gupnp-av-cp on each "player". That is an ARM BeagleBoard and a PowerPC
*unknown* board. Each will have a suitable display. Is this your
understanding/intention?

I guess Josh may go to bed now. :-)

btw, Darren, do we have to use real boards for the exercise? We don't have
those boards in PRC. Any limitations to use Qemu environments as the alternative
in our side?

Also it'd be great if we have a detail list for demo steps. Is it included in the
demo branch?

From: Darren Hart
Sent: Wednesday, October 20, 2010 8:24 AM

On 10/19/2010 05:16 PM, Joshua Lock wrote:

On Wed, 2010-10-20 at 01:04 +0100, Joshua Lock wrote:

On Tue, 2010-10-19 at 14:31 -0700, Saul Wold wrote:

Dongxiao,

Can you take a look at this since you have worked with the gstreamer?

I did a sloppy job pushing my changes when leaving the office but think
I have replicated most/all of the in the josh/demo branch.

I also took a look through the rygel code to see what gstreamer elements
are explicitly being used, I've created a list and tried to ensure as
many as possible of them are in the IMAGE_INSTALL list for
poky-image-rygel, adding them to the RDEPENDS for rygel doesn't appear
to have included them in the image I just created...

Full list of names of pipeline elements I found in the rygel code
follows:

decodebin2, videorate, videoscale, ffmpegcolorspace, ffenc_wmv1,
twolame, lame, mp3parse, ffenc_wmav2, convert-sink-pad,
ffenc_mpeg2video, audio-src-pad, audio-sink-pad, audio-enc-sink-pad,
sink, mpegtsmux, audioconvert, audioresample, audiorate, capsfilter,
audiotestsrc, videotestsrc, ffmux_asf

The image I just built with my latest changes in josh/demo worked!?!
Rygel did not segfault :-)

If you have time Dongxiao (or anyone else) I'd appreciate if you could
double-check my changes (my install_append in rygel to create a .config
isn't working, so you'll need to do that manually and run
rygel-preferences to disable the tracker plugin).
If you could test using Rygel as a renderer for some content served by
the mediatomb image, that would be much appreciated. You'll want
gupnp-av-cp as provided by gupnp-tools to control the renderer and
content server.

It is my udnerstanding that we plan to run both the renderer and the
gupnp-av-cp on each "player". That is an ARM BeagleBoard and a PowerPC
*unknown* board. Each will have a suitable display. Is this your
understanding/intention?

I guess Josh may go to bed now. :-)

btw, Darren, do we have to use real boards for the exercise? We don't have
those boards in PRC. Any limitations to use Qemu environments as the alternative
in our side?

Also it'd be great if we have a detail list for demo steps. Is it included in the
demo branch?

On Wed, 2010-10-20 at 01:04 +0100, Joshua Lock wrote:

On Tue, 2010-10-19 at 14:31 -0700, Saul Wold wrote:

Dongxiao,

Can you take a look at this since you have worked with the
gstreamer?

I did a sloppy job pushing my changes when leaving the office but
think I have replicated most/all of the in the josh/demo branch.

I also took a look through the rygel code to see what gstreamer
elements are explicitly being used, I've created a list and tried to
ensure as many as possible of them are in the IMAGE_INSTALL list for
poky-image-rygel, adding them to the RDEPENDS for rygel doesn't
appear to have included them in the image I just created...

Full list of names of pipeline elements I found in the rygel code
follows:

decodebin2, videorate, videoscale, ffmpegcolorspace, ffenc_wmv1,
twolame, lame, mp3parse, ffenc_wmav2, convert-sink-pad,
ffenc_mpeg2video, audio-src-pad, audio-sink-pad, audio-enc-sink-pad,
sink, mpegtsmux, audioconvert, audioresample, audiorate, capsfilter,
audiotestsrc, videotestsrc, ffmux_asf

The image I just built with my latest changes in josh/demo worked!?!
Rygel did not segfault :-)

If you have time Dongxiao (or anyone else) I'd appreciate if you
could double-check my changes (my install_append in rygel to create a
.config isn't working, so you'll need to do that manually and run
rygel-preferences to disable the tracker plugin). If you could test
using Rygel as a renderer for some content served by the mediatomb
image, that would be much appreciated. You'll want gupnp-av-cp as
provided by gupnp-tools to control the renderer and content server.

Thanks,
Joshua

Joshua Lock wrote:

On Wed, 2010-10-20 at 01:04 +0100, Joshua Lock wrote:

On Tue, 2010-10-19 at 14:31 -0700, Saul Wold wrote:

Dongxiao,

Can you take a look at this since you have worked with the
gstreamer?

I did a sloppy job pushing my changes when leaving the office but
think I have replicated most/all of the in the josh/demo branch.

I also took a look through the rygel code to see what gstreamer
elements are explicitly being used, I've created a list and tried to
ensure as many as possible of them are in the IMAGE_INSTALL list for
poky-image-rygel, adding them to the RDEPENDS for rygel doesn't
appear to have included them in the image I just created...

Full list of names of pipeline elements I found in the rygel code
follows:

decodebin2, videorate, videoscale, ffmpegcolorspace, ffenc_wmv1,
twolame, lame, mp3parse, ffenc_wmav2, convert-sink-pad,
ffenc_mpeg2video, audio-src-pad, audio-sink-pad, audio-enc-sink-pad,
sink, mpegtsmux, audioconvert, audioresample, audiorate, capsfilter,
audiotestsrc, videotestsrc, ffmux_asf

The image I just built with my latest changes in josh/demo worked!?!
Rygel did not segfault :-)

If you have time Dongxiao (or anyone else) I'd appreciate if you
could double-check my changes (my install_append in rygel to create a
.config isn't working, so you'll need to do that manually and run
rygel-preferences to disable the tracker plugin). If you could test
using Rygel as a renderer for some content served by the mediatomb
image, that would be much appreciated. You'll want gupnp-av-cp as
provided by gupnp-tools to control the renderer and content server.

Thanks,
Joshua

I will try your branch, however I didn't find josh/demo in poky-contrib.
Is it reside in other place?

On Tue, 2010-10-19 at 17:40 -0700, Xu, Dongxiao wrote:

Joshua Lock wrote:

On Wed, 2010-10-20 at 01:04 +0100, Joshua Lock wrote:

On Tue, 2010-10-19 at 14:31 -0700, Saul Wold wrote:

Dongxiao,

Can you take a look at this since you have worked with the
gstreamer?

I did a sloppy job pushing my changes when leaving the office but
think I have replicated most/all of the in the josh/demo branch.

I also took a look through the rygel code to see what gstreamer
elements are explicitly being used, I've created a list and tried
to ensure as many as possible of them are in the IMAGE_INSTALL list
for poky-image-rygel, adding them to the RDEPENDS for rygel doesn't
appear to have included them in the image I just created...

Full list of names of pipeline elements I found in the rygel code
follows:

decodebin2, videorate, videoscale, ffmpegcolorspace, ffenc_wmv1,
twolame, lame, mp3parse, ffenc_wmav2, convert-sink-pad,
ffenc_mpeg2video, audio-src-pad, audio-sink-pad,
audio-enc-sink-pad, sink, mpegtsmux, audioconvert, audioresample,
audiorate, capsfilter, audiotestsrc, videotestsrc, ffmux_asf

The image I just built with my latest changes in josh/demo
worked!?! Rygel did not segfault :-)

If you have time Dongxiao (or anyone else) I'd appreciate if you
could double-check my changes (my install_append in rygel to create
a .config isn't working, so you'll need to do that manually and run
rygel-preferences to disable the tracker plugin). If you could test
using Rygel as a renderer for some content served by the mediatomb
image, that would be much appreciated. You'll want gupnp-av-cp as
provided by gupnp-tools to control the renderer and content server.

Thanks,
Joshua

I will try your branch, however I didn't find josh/demo in
poky-contrib. Is it reside in other place?

It should be here:

ssh://git@.../meta-demo.git

Tom

Hi Josh,

Today I took a glance at the rygel crash issue in poky. Though I didn't
get the root cause, I found when configure Tracker plugin into rygel,
the segmentation fault will happen. Since we have already configured
the media-export plugin, and tracker plugin plays the same role, I
think we can simply disable tracker plugin (by configure time or change
by rygel-preferences) for demo usage.

Thanks,
Dongxiao

Xu, Dongxiao wrote:

I just built out the poky-image-rygel image with your meta-demo
layer, and run

rygel --gst-debug-level=5

I still saw it "segmentation fault" in the last...

I am looking into it.

Thanks,
Dongxiao

Xu, Dongxiao wrote:

Zanussi, Tom wrote:

On Tue, 2010-10-19 at 17:40 -0700, Xu, Dongxiao wrote:

Joshua Lock wrote:

On Wed, 2010-10-20 at 01:04 +0100, Joshua Lock wrote:

On Tue, 2010-10-19 at 14:31 -0700, Saul Wold wrote:

Dongxiao,

Can you take a look at this since you have worked with the
gstreamer?

I did a sloppy job pushing my changes when leaving the office but
think I have replicated most/all of the in the josh/demo branch.

I also took a look through the rygel code to see what gstreamer
elements are explicitly being used, I've created a list and tried
to ensure as many as possible of them are in the IMAGE_INSTALL
list for poky-image-rygel, adding them to the RDEPENDS for rygel
doesn't appear to have included them in the image I just
created...

Full list of names of pipeline elements I found in the rygel
code follows:

decodebin2, videorate, videoscale, ffmpegcolorspace, ffenc_wmv1,
twolame, lame, mp3parse, ffenc_wmav2, convert-sink-pad,
ffenc_mpeg2video, audio-src-pad, audio-sink-pad,
audio-enc-sink-pad, sink, mpegtsmux, audioconvert, audioresample,
audiorate, capsfilter, audiotestsrc, videotestsrc, ffmux_asf

The image I just built with my latest changes in josh/demo
worked!?! Rygel did not segfault :-)

If you have time Dongxiao (or anyone else) I'd appreciate if you
could double-check my changes (my install_append in rygel to
create a .config isn't working, so you'll need to do that
manually and run rygel-preferences to disable the tracker
plugin). If you could test using Rygel as a renderer for some
content served by the mediatomb image, that would be much
appreciated. You'll want gupnp-av-cp as provided by gupnp-tools
to control the renderer and content server.

Thanks,
Joshua

I will try your branch, however I didn't find josh/demo in
poky-contrib. Is it reside in other place?

It should be here:

ssh://git@.../meta-demo.git

Tom

Got it, thanks!

Dongxiao
_______________________________________________
yocto mailing list
yocto@...
https://lists.pokylinux.org/listinfo/yocto

On Wed, 2010-10-20 at 14:07 +0800, Xu, Dongxiao wrote:

Hi Josh,

Today I took a glance at the rygel crash issue in poky. Though I
didn't get the root cause, I found when configure Tracker plugin into
rygel, the segmentation fault will happen. Since we have already
configured the media-export plugin, and tracker plugin plays the same
role, I think we can simply disable tracker plugin (by configure time
or change by rygel-preferences) for demo usage.

Yes, I thought I mentioned disabling the tracker plugin in an earlier
mail? I'll prepare a patch to the recipe to disable that so we don't
have to remember to do that by hand.

Cheers,
Joshua

Thanks,
Dongxiao

Xu, Dongxiao wrote:

I just built out the poky-image-rygel image with your meta-demo
layer, and run

rygel --gst-debug-level=5

I still saw it "segmentation fault" in the last...

I am looking into it.

Thanks,
Dongxiao

Xu, Dongxiao wrote:

Zanussi, Tom wrote:

On Tue, 2010-10-19 at 17:40 -0700, Xu, Dongxiao wrote:

Joshua Lock wrote:

On Wed, 2010-10-20 at 01:04 +0100, Joshua Lock wrote:

On Tue, 2010-10-19 at 14:31 -0700, Saul Wold wrote:

Dongxiao,

Can you take a look at this since you have worked with the
gstreamer?

I did a sloppy job pushing my changes when leaving the office
but think I have replicated most/all of the in the josh/demo
branch.

I also took a look through the rygel code to see what gstreamer
elements are explicitly being used, I've created a list and
tried to ensure as many as possible of them are in the
IMAGE_INSTALL list for poky-image-rygel, adding them to the
RDEPENDS for rygel doesn't appear to have included them in the
image I just created...

Full list of names of pipeline elements I found in the rygel
code follows:

decodebin2, videorate, videoscale, ffmpegcolorspace,
ffenc_wmv1, twolame, lame, mp3parse, ffenc_wmav2,
convert-sink-pad, ffenc_mpeg2video, audio-src-pad,
audio-sink-pad, audio-enc-sink-pad, sink, mpegtsmux,
audioconvert, audioresample, audiorate, capsfilter,
audiotestsrc, videotestsrc, ffmux_asf

The image I just built with my latest changes in josh/demo
worked!?! Rygel did not segfault :-)

If you have time Dongxiao (or anyone else) I'd appreciate if you
could double-check my changes (my install_append in rygel to
create a .config isn't working, so you'll need to do that
manually and run rygel-preferences to disable the tracker
plugin). If you could test using Rygel as a renderer for some
content served by the mediatomb image, that would be much
appreciated. You'll want gupnp-av-cp as provided by gupnp-tools
to control the renderer and content server.

Thanks,
Joshua

I will try your branch, however I didn't find josh/demo in
poky-contrib. Is it reside in other place?

It should be here:

ssh://git@.../meta-demo.git

Tom

Got it, thanks!

Dongxiao
_______________________________________________
yocto mailing list
yocto@...
https://lists.pokylinux.org/listinfo/yocto

From: Richard Purdie
Sent: Wednesday, October 20, 2010 12:29 AM

On Tue, 2010-10-19 at 13:55 +0100, Richard Purdie wrote:

I've pushed some more invasive changes to the fetcher in the Poky master
branch. I'd appreciate the teams help in finding out if these work or
not, with both existing builds and with totally fresh from scratch
builds.

If they prove not to have major issues we're likely to merge these into
the release branch as what is there is going to bite people and look
rather bad.

There were some issues that Tom and Joshua were seeing which I debugged
and found that we weren't adding in new branches in the fetching code.

I was able to reproduce and then have added a patch to the git fetcher
which ensures these things are cloned correctly and any new branches are
created. I talked with Bruce to confirm my diagnosis and the solution.

This fix makes an awful lot of sense and explains various issues we've
been chasing for a while with the fetcher bugs so I'm very pleased to
have this fix checked in.

Could people continue to test the code and report any problems...

Hi Richard,
I have re-fixed this bug, please check it, thank you~

meta/recipes-extended/at/at_3.1.12.bb | 2
meta/recipes-extended/at/files/nonrootinstall.patch | 75 ------------------
meta/recipes-extended/at/files/nonstripbinaries.patch | 21 +++++
3 files changed, 22 insertions(+), 76 deletions(-)

Mei Lei (1):
at: remove nonrootinstall patch and modify relevant files

I tried "bitbake poky-image-sdk -c fetchall" both with an existing source directory
and with a fresh new download. Everything works fine.

Coming up to launch there are going to be some technical things that
need to be done, I'm aiming to write these down and assign owners so
we remember them all and that they all happen:

* Remove password protection from yoctoproject.org (sub)domains [RP]
* Swap default site redirection and name for lists.* and wiki.* [RP]
* Make meta-demo public [RP]
* Remove password protection from autobuilder [ScottG]
* Upload final version of the eclipse plugin [Jessica]
* Upload final Yocto release images and tarballs [???]

Coming up to launch there are going to be some technical things that
need to be done, I'm aiming to write these down and assign owners so we
remember them all and that they all happen:

* Remove password protection from yoctoproject.org (sub)domains [RP]
* Swap default site redirection and name for lists.* and wiki.* [RP]
* Make meta-demo public [RP]
* Remove password protection from autobuilder [ScottG]
* Upload final version of the eclipse plugin [Jessica]
* Upload final Yocto release images and tarballs [???]

What date and time are we going to actually do these things?

Cheers,

Richard



_______________________________________________
yocto mailing list
yocto@...
https://lists.pokylinux.org/listinfo/yocto

Coming up to launch there are going to be some technical things that
need to be done, I'm aiming to write these down and assign owners so we
remember them all and that they all happen:

* Remove password protection from yoctoproject.org (sub)domains [RP]
* Swap default site redirection and name for lists.* and wiki.* [RP]
* Make meta-demo public [RP]
* Remove password protection from autobuilder [ScottG]
* Upload final version of the eclipse plugin [Jessica]
* Upload final Yocto release images and tarballs [???]

What date and time are we going to actually do these things?