All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: Yocto Project <yocto@yoctoproject.org>
Cc: Josh Lock <joshua.lock@intel.com>,
	"Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
Subject: RFC: "Demo Use Cases" documentation for the web page
Date: Thu, 21 Oct 2010 16:00:41 -0700	[thread overview]
Message-ID: <4CC0C619.7070201@linux.intel.com> (raw)


Media Network Demo
==================
We're looking to have a section on the web site for the demo that
explains what each use-case is and possibly how it can be replicated.
I'm taking the approach of describing each image. Consider the
following:

The Yocto Project launch event at ECLF 2010 featured a
multi-architecture Media Network Demo. All the source for this demo is
available in the meta-demo git repository as a layer for the poky build
system.

The following images made up the demo:
o poky-image-nas
o poky-image-mediatomb
o poky-image-rygel

poky-image-nas
--------------
The poky-image-nas image boots your device as a network attached storage
device. It provides a DHCP service and an NFS server. We used this image
to store all our media.

poky-image-mediatomb
--------------------
The poky-image-mediatomb image adds a UPnP content provider via the
mediatomb package. This image mounts the media share from the NAS and
makes it available to UPnP renderers.

poky-image-rygel
----------------
The poky-image-rygel image provides gupnp tools and the rygel media
renderer along with the sato desktop. The renderer can be controlled 
locally or via any control point on the network. Several devices can run 
this image and stream media from the mediatomb device.


Open Questions
--------------
o Is this more or less what we are looking for?
o Should we modify the mediatomb image to:
   o automatically mount a specific share from the NAS?
   o add something to the config to automatically scan the
     media share?
o The poky-image-rygel description needs to be updated as we finalize
   the package.



-- 
Darren Hart
Embedded Linux Kernel


             reply	other threads:[~2010-10-21 23:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-21 23:00 Darren Hart [this message]
2010-10-22  0:26 ` RFC: "Demo Use Cases" documentation for the web page Tian, Kevin
2010-10-22 20:22   ` Darren Hart
2010-10-22 21:04     ` Alex deVries
2010-10-22 22:04       ` Darren Hart
2010-10-22 22:17         ` Mark Hatle
2010-10-22 22:21           ` Mark Hatle
2010-10-22  1:32 ` Tom Zanussi
2010-10-22 17:35 ` Stewart, David C
2010-10-22 17:44   ` Dirk Hohndel
2010-10-22 17:51   ` Mark Hatle
2010-10-22 22:02 ` RFC V2: " 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=4CC0C619.7070201@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=joshua.lock@intel.com \
    --cc=scott.m.rifenbark@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.