From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot at ELC: review/suggestions needed
Date: Mon, 11 Feb 2013 09:42:06 +0100 [thread overview]
Message-ID: <20130211094206.7b9a4c53@skate> (raw)
In-Reply-To: <CAAfyv37Orrms8Jz1jLUg1BOCf0eD0HJzy1rK+y+S056m9BzFFg@mail.gmail.com>
Dear Belisko Marek,
On Sun, 10 Feb 2013 13:46:25 +0100, Belisko Marek wrote:
> > * Review the Buildroot poster I've made. The poster will be
> > printed by the event organizers in big format, and I've tried to
> > highlight the main fact about Buildroot, and recent developments.
> Poster is great. Maybe one comment: why only Google Fiber is mention
> as product which
> using BR? Isn't there any other companies (products)?
There are of course many more companies using Buildroot, and we've
discussed this during the last Buildroot Developers meeting: in the
next version of the Buildroot website, we'll have a place to list
companies/products using Buildroot.
Regarding the poster itself, there are multiple reasons for choosing
this example:
* Google is a well-known company, and generally developers are
"impressed" by what Google does. So having Google using Buildroot is
"waouh".
* The Buildroot code that Google uses is public and clearly associated
to the Google Fiber project, which means that Google is OK with the
people knowing that Buildroot is used. Many other companies that are
using Buildroot are not so public with the fact that they use
Buildroot.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-02-11 8:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 18:57 [Buildroot] Buildroot at ELC: review/suggestions needed Thomas Petazzoni
2013-02-09 19:06 ` Thomas Petazzoni
2013-02-09 23:47 ` Yann E. MORIN
2013-02-10 9:50 ` Peter Korsgaard
2013-02-10 10:59 ` Yann E. MORIN
2013-02-11 8:24 ` Thomas Petazzoni
2013-02-11 9:51 ` Will Newton
2013-02-11 10:31 ` Thomas Petazzoni
2013-02-11 17:34 ` Luca Ceresoli
2013-02-10 11:28 ` Stephan Hoffmann
2013-02-11 8:26 ` Thomas Petazzoni
2013-02-10 12:46 ` Belisko Marek
2013-02-11 8:42 ` Thomas Petazzoni [this message]
2013-02-11 8:33 ` Yegor Yefremov
2013-02-11 13:38 ` Shawn J. Goff
2013-02-24 4:07 ` Thomas Petazzoni
2013-02-13 22:13 ` Thomas Petazzoni
2013-02-13 22:57 ` Yann E. MORIN
2013-02-13 23:13 ` Arnout Vandecappelle
2013-02-14 5:35 ` Baruch Siach
2013-02-14 9:46 ` Thomas Petazzoni
2013-02-14 9:54 ` Jeremy Rosen
2013-02-14 9:58 ` Thomas Petazzoni
2013-02-14 12:34 ` Baruch Siach
2013-02-14 9:53 ` Will Moore
2013-02-14 10:05 ` Thomas Petazzoni
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=20130211094206.7b9a4c53@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox