From: eric <eric@eric-weiss.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Call for demos
Date: Thu, 02 Jan 2014 11:58:12 +0000 [thread overview]
Message-ID: <52C55454.204@eric-weiss.de> (raw)
In-Reply-To: <52C4AD81.8070803@balister.org>
On 01/02/14 00:06, Philip Balister wrote:
> I was thinking about demos for FOSDEM (thanks to the people that have
> already offered some) and realized I should reach out to the broader
> community.
>
> OpenEmbedded has a stand (table) at FOSDEM to show of the project to the
> oen source community. Typically, whoever comes to FOSDEM brings whatever
> cool thing they are working on with OE at the time. I'd liek to try and
> get some more diverse hardware on display to show how flexible the
> project is.
>
> A good demo should be visually interesting. Blinking lights/ LCD panels
> etc. A few static seriously embedded things are fine, but people love to
> see blinking lights :)
>
> Long term, I'd like to build up a set of physically small demos we can
> pass around as people attend various conferences to show off
> OpenEmbedded (and the Yocto Project) capabilities.
>
> What I am looking for is boards with good BSP layers that are well
> supported (preferably by the manufacturer in some way) and have an image
> that is easy for people to reproduce. (Basically, we should show stuff
> that people can go home, order hardware, and build the demo image
> without a lot of tweaking).
>
> So what I am looking for is:
>
> 1) Donations of hardware we can demo
> 2) Software support for the hardware
i would like to bring in an ouya game console ( need and hdmi for
monitor it )
and maybe ( depends on if i get repaired the display glass right in
time) an asus tf201 transformer.
> I'd like to use this as a way for us to show support for vendors that
> support us.
>
> Philip
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>
next prev parent reply other threads:[~2014-01-02 11:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-02 0:06 Call for demos Philip Balister
2014-01-02 11:58 ` eric [this message]
2014-01-02 12:34 ` Alex J Lennon
2014-01-02 13:36 ` Philip Balister
2014-01-02 14:00 ` Alex J Lennon
2014-01-02 12:47 ` [oe] " Paul Barker
2014-01-02 12:47 ` Paul Barker
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=52C55454.204@eric-weiss.de \
--to=eric@eric-weiss.de \
--cc=openembedded-devel@lists.openembedded.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.