From: Darren Hart <dvhart@linux.intel.com>
To: Yocto Project <yocto@yoctoproject.org>
Cc: Josh Lock <joshua.lock@intel.com>
Subject: Media Network Demo: Black Sand and Netbook
Date: Thu, 21 Oct 2010 15:44:34 -0700 [thread overview]
Message-ID: <4CC0C252.1020501@linux.intel.com> (raw)
I build mediatomb and rygel live atom-pc images from today's poky/master
+ meta-demo/master. I booted mediatomb on the BlackSand and rygel on the
netbook. I had to manually start the rygel renderer on the netbook. I
didn't see gupnp-av-cp on the rygel image as I expected and the
gupnp-universal-cp command failed to start on the netbook (via a sato
terminal) complaining about missing icons. If I tried to stabrt this
over an ssh - connection, the gupnp-universal-cp started fine (strange).
I could run gupnp-av-cp from my laptop (Ubuntu 10.10) and play music
from mediatomb on the rygel renderer. (YAY)
What I'd like to see is for gupnp-av-cp to start automatically after the
sato desktop loads on each renderer. This would make each renderer a
standalone player.
So, it's functional (awesome!) and I see these ARs as pending for the
demo images:
[ ] add gupnp-av-cp to the rygel image
[ ] start rygel on boot (after networking)
[ ] start gupnp-av-cp after the sato desktop loads on the rygel image
[ ] setup networking on each of the non-nas images to dhcp on eth0
With the above, each image should boot to a functional state with no
manual interference required.
How much of the above is already planned and how much do we need to get
an owner for?
--
Darren Hart
Embedded Linux Kernel
next reply other threads:[~2010-10-21 22:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 22:44 Darren Hart [this message]
2010-10-21 23:29 ` Media Network Demo: Black Sand and Netbook Tom Zanussi
2010-10-22 7:29 ` Joshua Lock
2010-10-22 15:54 ` Darren Hart
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=4CC0C252.1020501@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=joshua.lock@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.