On Tue, 2010-10-19 at 08:40 -0700, Stewart, David C wrote:

* demo

** Alex will put the hardware bits together, Darren to write down the description of what needs to come together and wiki-fy it. RP suggests that maybe getting all the pieces running on one hardware might be a good way to try it out just in case.

I can try getting everything running on one machine too - would it make
sense to try that all on e.g. emenlow, or all on a laptop using qemu, or
both?

Tom

On 10/19/10 4:01 PM, Alex deVries wrote:

On 2010-10-19, at 11:40 AM, Stewart, David C wrote:

** Alex will put the hardware bits together, Darren to write down the description of what needs to come together and wiki-fy it.

Yes, so what I need is something like:

- description
- expected behaviour
- hardware used
- how to build and install the software

... for all four boards. The sooner we have something, the sooner I can start.

Does that make sense, Darren?

Darren (or someone else can correct me.. but what I'm doing now)

Board: RouterStationPro
Purpose: NAS and boot server for other board
Features:
- Contains file server for multimedia and other files
- Can serve files via:
- NFS
- http

- tftp (likely needed if the other boards need to network boot)
- ftp (maybe)

- Will act as THE authoritation DHCP server for the network of boards
- no DNS on the network (is it needed?)

Software:
- From the meta-demo, build the poky-image-nas with the machine target of the
routerstationpro (thats the goal, but there might be some custom config files
in the end.. still working on it)

I thought the plan was to do BOTH a QEMU demo and a demo on real
hardware? If that's not the plan, it should be the plan.

On 10/19/10 4:01 PM, Alex deVries wrote:

On 2010-10-19, at 11:40 AM, Stewart, David C wrote:

** Alex will put the hardware bits together, Darren to write down the description of what needs to come together and wiki-fy it.

Yes, so what I need is something like:

- description
- expected behaviour
- hardware used
- how to build and install the software

... for all four boards. The sooner we have something, the sooner I can start.

Does that make sense, Darren?

Darren (or someone else can correct me.. but what I'm doing now)

Board: RouterStationPro
Purpose: NAS and boot server for other board
Features:
- Contains file server for multimedia and other files
- Can serve files via:
- NFS
- http

- tftp (likely needed if the other boards need to network boot)
- ftp (maybe)

- Will act as THE authoritation DHCP server for the network of boards
- no DNS on the network (is it needed?)

Software:
- From the meta-demo, build the poky-image-nas with the machine target of the
routerstationpro (thats the goal, but there might be some custom config files
in the end.. still working on it)

I thought the plan was to do BOTH a QEMU demo and a demo on real
hardware? If that's not the plan, it should be the plan.

On 10/19/2010 09:04 AM, Zanussi, Tom wrote:

On Tue, 2010-10-19 at 08:40 -0700, Stewart, David C wrote:

* demo

** Alex will put the hardware bits together, Darren to write down the description of what needs to come together and wiki-fy it. RP suggests that maybe getting all the pieces running on one hardware might be a good way to try it out just in case.

I can try getting everything running on one machine too - would it make
sense to try that all on e.g. emenlow, or all on a laptop using qemu, or
both?

Everything on One machine doesn't make a lot of sense to me, for two
reasons:

1) This is heavily network dependent, making sure the machines can find
eachother is a critical aspect of testing this.
2) Qemu does some magic with tun/tap devices, you have to configure
things to get multicast working between guests. I've tested the
mediatomb image in qemu, it works. We need to test on real hardware.
3) We don't an image that will install everything on the same machine,
and making one doesn't make a lot of sense to me.
4) Running a NAS to serve up media to itself doesn't test the networking
side of things as well.

I'd rather use 3 real devices (even if they are all emenlow or
blacksand) rather than qemu or all on one.

--
Darren

Tom

On 10/19/2010 02:48 PM, Anderson, Paul wrote:

I thought the plan was to do BOTH a QEMU demo and a demo on real
hardware? If that's not the plan, it should be the plan.

There has been no discussion of a QEMU demo for the media network demo.
I've tested some components with QEMU, but we aren't currently planning
on demo'ing this in QEMU.

David, Kevin, Paul, Richard:

As discussed in the project sync we need to do a readiness review to
look at the current state of the release with regards to existing open
bugs, QA testing, and general sanity of the release.

The best time for this would be Thursday morning at 11:00, could the
folks on the "To:" line please respond with your availablity to meet at
this time. We need to do it in the morning to enable Richard to attend
at a "reasonable" hour.


Thursday Oct 21, 2010 11:00AM
Where: 916-356-2663, 8-356-2663 Bridge 92 / 3302969

Thanks
Sau!

On 10/19/10 5:13 PM, Saul Wold wrote:

David, Kevin, Paul, Richard:

As discussed in the project sync we need to do a readiness review to
look at the current state of the release with regards to existing open
bugs, QA testing, and general sanity of the release.

The best time for this would be Thursday morning at 11:00, could the
folks on the "To:" line please respond with your availablity to meet at
this time. We need to do it in the morning to enable Richard to attend
at a "reasonable" hour.


Thursday Oct 21, 2010 11:00AM
Where: 916-356-2663, 8-356-2663 Bridge 92 / 3302969

11am Pacific should work.. I have a short meeting somewhere between 2 and 6
EDT... (or 10 and 2 Pacific).. Hopefully this won't interfere.. (sorry I don't
have details beyond that wide range.. but it's supposed to be 15 minutes or
less) :P

--Mark

Thanks
Sau!

David, Kevin, Paul, Richard:

As discussed in the project sync we need to do a readiness review to
look at the current state of the release with regards to existing open
bugs, QA testing, and general sanity of the release.

The best time for this would be Thursday morning at 11:00, could the
folks on the "To:" line please respond with your availablity to meet at
this time. We need to do it in the morning to enable Richard to attend
at a "reasonable" hour.


Thursday Oct 21, 2010 11:00AM
Where: 916-356-2663, 8-356-2663 Bridge 92 / 3302969

Dongxiao,

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

Thanks
Sau!


On 10/19/2010 02:15 PM, Joshua Lock wrote:

Hi all,

I've packaged Rygel, a upnp media server and renderer, to use as the
media renderer in the upnp demo. However I'm seeing a segfault at launch
and as it's getting late here I'm wondering if someone in a strategic
timezone can help debug while I cycle home and sleep.

The (ugly) recipes are in the josh/demo branch of the meta-demo
repository.

rygel --gst-debug-level=5

shows plenty of output, but nothing that jumps out to a gstreamer newb
like me. AFAICT I have all of the plugins required but it's possible we
need to add more.

If not I'll pick it up again in the morning.

Thanks,
Joshua

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

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 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

Cheers,
Joshua

Thanks
Sau!


On 10/19/2010 02:15 PM, Joshua Lock wrote:

Hi all,

I've packaged Rygel, a upnp media server and renderer, to use as the
media renderer in the upnp demo. However I'm seeing a segfault at launch
and as it's getting late here I'm wondering if someone in a strategic
timezone can help debug while I cycle home and sleep.

The (ugly) recipes are in the josh/demo branch of the meta-demo
repository.

rygel --gst-debug-level=5

shows plenty of output, but nothing that jumps out to a gstreamer newb
like me. AFAICT I have all of the plugins required but it's possible we
need to add more.

If not I'll pick it up again in the morning.

Thanks,
Joshua

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

--
Joshua Lock
Intel Open Source Technology Centre

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

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