All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Tian, Kevin" <kevin.tian@intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: UPnP demo - call for testing
Date: Wed, 20 Oct 2010 23:28:15 -0400	[thread overview]
Message-ID: <4CBFB34F.7080108@windriver.com> (raw)
In-Reply-To: <625BA99ED14B2D499DC4E29D8138F1504D0149B25A@shsmsx502.ccr.corp.intel.com>

On 10-10-20 10:53 PM, Tian, Kevin wrote:
>> From: Joshua Lock
>> Sent: Thursday, October 21, 2010 1:19 AM
>>
>> Hi all,
>>
>> I've successfully tested the UPnP demo in my office but would appreciate
>> someone else taking a bash.
>>
>> Unfortunately you currently need my branch from poky-contrib (josh/demo)
>> and the corresponding branch from meta-demo (josh/demo).
>>
>> The renderer and controller are installed together in the
>> poky-image-rygel image (I've been using the -live variant).
>>
>> I needed to use amixer to enable the soundcard and increase the volume
>> on the netbook I was using.
>>
>> "amixer set Master on
>> amixer set Master 75"
>>
>> Run rygel from a terminal and launch gupnp-av-cp and you should be able
>> to set play music from a content store on the device. I haven't tested
>> video...
>>
>> I need to tweak the recipes some more so that:
>> * Rygel is configured and started automatically at boot on the rygel
>> image
>> * All of the required recipes are self contained in the master branch
>> meta-demo overlay.
>>
>> I think this may mean using bbappend to extend recipes where I've
>> currently modified them in the main meta overlay, rather than
>> replication a recipe with the same PN and PV.
>>
>> I'll probably work on this tomorrow.
>>
>
> I'd like to understand a full picture of this demo just in case others are
> also interested in the test. From what I read so far:
> 	Mark works on an NAS server
> 	Darren covers a media server with mediatomb
> 	Josh sits on UPnP renderer/controller with rygel and gupnp tools
>
> So is the demo chained as below:
>
> NAS server provides media contents which are then found and exported
> by mediatomb which then are found by UPnP controller which then points to
> the UPnP renderer for final output. Here UPnP controller and renderer may
> or may not be the same board.
>
> what Josh wants people to test here is self-contained in one image which
> contains both renderer/controller and server (local media files), which hasn't
> been connected to other bits yet.
>
> Is above understanding correct?

That matches my understanding.

Bruce

>
> Thanks,
> Kevin
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.pokylinux.org/listinfo/yocto



  reply	other threads:[~2010-10-21  3:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-20 17:18 UPnP demo - call for testing Joshua Lock
2010-10-20 17:22 ` Kamble, Nitin A
2010-10-20 22:09 ` Joshua Lock
2010-10-20 23:48   ` Darren Hart
2010-10-21  0:07     ` Tom Zanussi
2010-10-21  0:12       ` Darren Hart
2010-10-21 11:09     ` Joshua Lock
2010-10-21  1:23 ` Xu, Dongxiao
2010-10-21  5:32   ` Xu, Dongxiao
2010-10-21 10:50     ` Joshua Lock
2010-10-21 13:14       ` Xu, Dongxiao
2010-10-21 16:26       ` Darren Hart
2010-10-21  2:53 ` Tian, Kevin
2010-10-21  3:28   ` Bruce Ashfield [this message]
2010-10-21 14:52 ` Tom Zanussi
2010-10-21 15:01   ` Joshua Lock
2010-10-21 15:12   ` Stewart, David C
2010-10-21 15:38   ` Mark Hatle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4CBFB34F.7080108@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=kevin.tian@intel.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.