From: Cyril HAENEL <chaenel@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] Which commercial products use buildroot?
Date: Sun, 11 Apr 2010 14:08:29 +0200 [thread overview]
Message-ID: <4BC1BBBD.3000703@free.fr> (raw)
In-Reply-To: <w2k2facd6dc1004110431idf465b71za05aef84eed86ad4@mail.gmail.com>
Hi,
There is at least my product I developped for the french laboratory
"Arc'Antique", which is specialized in heritage restauration.
The product do controlled high power electrolysis on metalic heritage
piece collected in the sea to restore them. Configuration and
supervision are done through web pages (with ethernet, wifi, gprs or pstn).
I use buildroot-2009.05 on an Arm AT91SAM9260 processor, associed with
64MiB SDRAM and 512MiB Nand flash (jffs2 filesystem).
Regards,
Cyril HAENEL
Tom Parkin a ?crit :
> Hi list,
>
> I'm doing some research into embedded Linux distributions as a
> background to an article I'm planning on the various embedded distros
> and their areas of application. Particularly, I'm interested in
> finding out about any commercial products which have used a particular
> distribution in their software stack -- I think such examples will
> help give my audience something extra to relate to, particularly if
> they are widely known examples.
>
> As such, I was wondering whether you know of any products which use
> buildroot?
>
> Many thanks for your help,
> Tom
>
--
Cyril Haenel
Registered Linux User #332632
-------------- next part --------------
A non-text attachment was scrubbed...
Name: _jga6772petit.jpg
Type: image/jpeg
Size: 424236 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100411/dd4ac012/attachment-0005.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imgp1193.jpg
Type: image/jpeg
Size: 482140 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100411/dd4ac012/attachment-0006.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imgp1210.jpg
Type: image/jpeg
Size: 439323 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100411/dd4ac012/attachment-0007.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imgp1218.jpg
Type: image/jpeg
Size: 347808 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100411/dd4ac012/attachment-0008.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imgp1221.jpg
Type: image/jpeg
Size: 388285 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20100411/dd4ac012/attachment-0009.jpg>
next prev parent reply other threads:[~2010-04-11 12:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-11 11:31 [Buildroot] Which commercial products use buildroot? Tom Parkin
2010-04-11 12:08 ` Cyril HAENEL [this message]
2010-04-11 15:14 ` Tom Parkin
2010-04-11 18:10 ` Cyril HAENEL
2010-08-02 15:29 ` [Buildroot] Auto standby after 10 minutes, what origin? Damien Borie
2010-04-12 14:16 ` [Buildroot] Which commercial products use buildroot? Peter Korsgaard
2010-04-12 14:46 ` Will Newton
2010-04-12 15:10 ` Thomas Petazzoni
2010-04-12 15:58 ` Steve Calfee
2010-04-14 21:27 ` Tom Parkin
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=4BC1BBBD.3000703@free.fr \
--to=chaenel@free.fr \
--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