From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by mx1.pokylinux.org (Postfix) with ESMTP id 1FAF24C80121 for ; Tue, 19 Oct 2010 19:34:28 -0500 (CDT) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 19 Oct 2010 17:34:27 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.57,353,1283756400"; d="scan'208";a="668982062" Received: from unknown (HELO [10.255.12.104]) ([10.255.12.104]) by orsmga001.jf.intel.com with ESMTP; 19 Oct 2010 17:34:27 -0700 Message-ID: <4CBE3913.8090903@linux.intel.com> Date: Tue, 19 Oct 2010 17:34:27 -0700 From: Darren Hart User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.9) Gecko/20100922 Thunderbird/3.1.4 MIME-Version: 1.0 To: "Tian, Kevin" References: <1287522903.24666.5.camel@scimitar> <4CBE0E4A.1050208@intel.com> <1287533087.2283.5.camel@scimitar> <1287533773.2283.10.camel@scimitar> <4CBE3693.2070808@linux.intel.com> <625BA99ED14B2D499DC4E29D8138F1504CF2575B86@shsmsx502.ccr.corp.intel.com> In-Reply-To: <625BA99ED14B2D499DC4E29D8138F1504CF2575B86@shsmsx502.ccr.corp.intel.com> Cc: "yocto@yoctoproject.org" Subject: Re: Call for help for demo UPNP media renderer X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Oct 2010 00:34:28 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 10/19/2010 05:30 PM, Tian, Kevin wrote: >> 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? For testing the images, you can use all x86 hardware. I'd prefer we not use QEMU as it is likely to complicate the networking, which is rather integral to this demo. > > Also it'd be great if we have a detail list for demo steps. Is it included in the > demo branch? No documented steps yet, just build the live images in the demo layers and boot on hardware. If you run into issues, please share them here and we'll help work through them. Thanks, -- Darren Hart Embedded Linux Kernel