All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Ulf Samuelsson <openembedded-core@emagii.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Stand for FOSDEM
Date: Wed, 16 Jan 2013 16:38:49 +0000	[thread overview]
Message-ID: <1985382.IITHNa7hCZ@helios> (raw)
In-Reply-To: <50F338E5.1030905@emagii.com>

On Sunday 13 January 2013 23:44:53 Ulf Samuelsson wrote:
> Plan to be there.
> Hopefully I should be able to arrange another Atmel raffle,
> to draw people to the stand.

That would be awesome!

> Do we have any plans for demo's?

Nothing solid yet, but thinking about it I'd like to have something around 5 
devices on show, preferably showing the range of different targets we support, 
and ideally the each of them should be doing something interesting. I'm going 
to try and bring along an x86-powered device, and have access to various other 
devices although I'm not sure I can come up with demos to run on each so 
suggestions/help would be welcome. 

For the last FOSDEM, Alex Lennon was kind enough to bring along his radar 
detector that was powered by OE, and I think that worked quite well as a demo. 
If at all possible it would be great if we could not just have dev boards but 
some actual products powered by OE on the stand. Can anyone help with that?

We probably also want to be prepared to do demos of configuring / running a 
build, with the usual assumption that we might not have a reliable internet 
connection. I think I can take care of setting this up.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre



      reply	other threads:[~2013-01-16 16:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-20 21:08 Stand for FOSDEM Philip Balister
2012-11-20 22:26 ` Paul Eggleton
2013-01-13 22:44   ` Ulf Samuelsson
2013-01-16 16:38     ` Paul Eggleton [this message]

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=1985382.IITHNa7hCZ@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@emagii.com \
    --cc=openembedded-core@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.