All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: jfabernathy <jfabernathy@gmail.com>
Cc: "meta-ti@yoctoproject.org" <meta-ti@yoctoproject.org>
Subject: Re: building Yocto for Pandaboard
Date: Thu, 09 Feb 2012 08:53:42 -0800	[thread overview]
Message-ID: <4F33FA16.4060402@balister.org> (raw)
In-Reply-To: <4F33F4A0.6010303@gmail.com>

On 02/09/2012 08:30 AM, jfabernathy wrote:

...

>> Richard
>>
> When you look at Yocto project from a marketing point of view, which is
> not something the open source community usually concentrates on for
> obvious reasons, it would be a very positive message to be able to talk
> about, and demonstrate with examples of taking the same project and
> moving it from one architecture to another with minimal effort, as long
> as both architectures supported the key features like media playback
> acceleration, 3D, sound, HDMI, etc.
> 

Actually, at least some of us in the open source community pay close
attention to marketing.

> While hardware companies tend to cringe when you make it too easy to
> move back and forth, the reality is, if you have a high volume product
> you can't justify or afford to throw excess performance, thermals,
> power, and cost where it is not needed.  For example a cheap digital
> signage application that just throws advertisement, or menu data on the
> screen could be done with an ARM processor like OMP3/4, but if you had a
> higher end product that needed to do extensive video analytics for
> customer profiling and advertising effectiveness, you're going to want a
> Core i5/i7.  It would be of great benefit to take the Yocto project that
> did the digital sign on the ARM and quickly get it up and running on the
> Core i5 and then concentrate on the analytics application.
> 
> I think this portability is a better sell, if it's all Yocto.  We all
> know that really smart people can move around from different Linux
> versions and development methods, but it's an easier sale to a customer
> management when you say it can all be done on Yocto and that it's easily
> demonstrated.

Yocto is becoming a very overloaded word at the moment. But the key idea
is that we can focus on building out from oe-core to support our
products using the same tools, no matter what the product scale. From
very simple devices to products that resemble their desktop brothers.

Philip

> 
> JIm A
> 
>>
>>
>>
> 
> _______________________________________________
> meta-ti mailing list
> meta-ti@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-ti
> 


  parent reply	other threads:[~2012-02-09 16:53 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08 21:58 building Yocto for Pandaboard jfabernathy
2012-02-08 22:04 ` Koen Kooi
2012-02-08 22:05 ` Gary Thomas
2012-02-08 22:11   ` jfabernathy
2012-02-08 22:18     ` Koen Kooi
2012-02-08 22:22       ` Gary Thomas
2012-02-08 22:27         ` Koen Kooi
2012-02-08 22:34           ` Gary Thomas
2012-02-08 22:51             ` James Abernathy
2012-02-09  1:16               ` William Mills
     [not found]                 ` <CAFZh4h_dVaOnbYMZjnAc34upJqoPKK4AaPEOEHPTQL6ZEyU-6w@mail.gmail.com>
2012-02-09 16:23                   ` Brian Hutchinson
2012-02-09 16:36                     ` Denys Dmytriyenko
2012-02-09 16:54                       ` Brian Hutchinson
2012-02-09 17:53                         ` Denys Dmytriyenko
2012-02-09 16:59                       ` Philip Balister
2012-02-09 17:05                         ` Brian Hutchinson
2012-02-09 18:17                           ` Jeff Osier-Mixon
2012-02-09 18:20                             ` Denys Dmytriyenko
2012-02-09 18:23                               ` Jeff Osier-Mixon
2012-02-09 17:12                         ` Gary Thomas
2012-02-09 17:15                           ` Denys Dmytriyenko
2012-02-09 17:25                             ` Gary Thomas
2012-02-09 17:14                         ` Denys Dmytriyenko
2012-02-09 13:01               ` Maupin, Chase
2012-02-09 13:11                 ` jfabernathy
2012-02-09 13:54                   ` Koen Kooi
2012-02-09 15:21                     ` Maupin, Chase
2012-02-09 15:33                     ` Richard Purdie
2012-02-09 16:30                       ` jfabernathy
2012-02-09 16:36                         ` Jack Mitchell
2012-02-09 16:53                         ` Philip Balister [this message]
2012-02-09 16:57                       ` Denys Dmytriyenko
2012-02-08 22:20     ` Gary Thomas
  -- strict thread matches above, loose matches on Subject: below --
2012-02-27  8:26 Building " Christian.Schulenberg
2012-02-27  8:50 ` Koen Kooi
2012-02-27 16:06   ` Philip Balister
2012-02-27 16:19     ` Koen Kooi
2012-02-27 17:06       ` William Mills
2012-02-27 18:56         ` Denys Dmytriyenko
2012-02-28  7:52         ` Christian.Schulenberg
2012-02-28  7:56           ` Koen Kooi
2012-02-28  8:15             ` Christian.Schulenberg
2012-03-05  8:58               ` Christian.Schulenberg
2012-03-05 13:04                 ` Robert P. J. Day
2012-03-05 14:21                   ` Christian.Schulenberg
2012-03-05 15:16                     ` Robert P. J. Day
2012-03-05 15:29                       ` Christian.Schulenberg
2012-03-05 15:48                         ` Robert P. J. Day
2012-03-05 16:39                     ` Robert P. J. Day
2012-03-05 16:43                       ` Gary Thomas
2012-03-05 16:58                         ` Denys Dmytriyenko
2012-03-05 17:13                           ` Robert P. J. Day
2012-03-05 17:15                             ` Koen Kooi
2012-03-05 20:29                               ` Denys Dmytriyenko
2012-03-05 20:31                                 ` Koen Kooi
2012-03-05 22:28                                   ` Denys Dmytriyenko
2012-03-06  1:39                                     ` Denys Dmytriyenko
2012-03-06  2:20                                       ` Brian Hutchinson
2012-03-05 20:26                             ` Marc Butler

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=4F33FA16.4060402@balister.org \
    --to=philip@balister.org \
    --cc=jfabernathy@gmail.com \
    --cc=meta-ti@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.