From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Angelo Compagnucci <angelo.compagnucci@gmail.com>
Cc: buildroot@buildroot.org, Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH v4 2/3] website: add a showcase page
Date: Sat, 07 Nov 2026 15:06:19 +0100 [thread overview]
Message-ID: <23bd9f8e90ca12911336ca571708b3ea@free.fr> (raw)
In-Reply-To: <20261106111604.1500074-2-angelo.compagnucci@gmail.com>
Hi Angelo,
Thanks for this patch. I have few suggestions, see below.
On 06/11/2026 12:16, Angelo Compagnucci wrote:
> Add a page listing products and projects whose operating system is
> built with Buildroot, each one with a link to a public source:
>
> - well known products: Tesla, Home Assistant OS, Sipeed NanoKVM and
> Analog Devices ADALM-PLUTO;
> - testimonials from Arm, Home Assistant OS, EVS and Texas Instruments,
> quoted from the Buildroot at 25 talk at ELC Europe 2026;
> - open source projects: Batocera.linux, Recalbox, OpenIPC, Thingino,
> minikube, Nerves, SeedSigner OS, SkiffOS and Tomato64;
> - vendor SDKs: Texas Instruments, Microchip, STMicroelectronics,
> Analog Devices, Canaan Kendryte K230, StarFive JH7110 and Espressif
> ESP32-S31.
>
> The page ends by inviting users to tell about their products on the
> mailing list.
>
> Signed-off-by: Angelo Compagnucci <angelo.compagnucci@gmail.com>
> ---
> Changes v3 -> v4:
> - add a "What users say" section, quoting verbatim the testimonials
> collected for the Buildroot at 25 talk at ELC Europe 2026 (Arm,
> Home
> Assistant OS, EVS and Texas Instruments), with a link to the
> published slides; the EVS one is shortened to fit the layout;
> - projects: drop MiSTer FPGA, whose Linux image repository is barely
> known, and add Tomato64, which also gave a testimonial for the
> talk.
>
> Changes v2 -> v3:
> - reorganize the page to prioritize active projects, each one
> checked against its public repository, documentation or
> image [Thomas]:
> - tagline: "From cars and smart homes to cameras and retro
> consoles";
> - well known: keep Tesla even if it is old, because its Buildroot
> tree is still public and verifiable on GitHub; describe it as the
> tree building the infotainment and Autopilot images;
> - well known: mention the br2-external tree of Home Assistant OS
> and link its GitHub repository; replace Google Fiber and GoPro
> with Sipeed NanoKVM and Analog Devices ADALM-PLUTO;
> - projects: drop KNULLI, RaspberryMatic, OpenWrt (not Buildroot
> based anymore), Kerberos.io KiOS (archived) and Open Voice OS
> (barely active); add MiSTer FPGA, Thingino, minikube,
> SeedSigner OS and SkiffOS; reword Recalbox;
> - vendor SDKs: drop Rockchip (only a Web Archive copy of its guide
> is left); update the Texas Instruments link to SDK 12.01 and the
> Microchip link to the linux4microchip repository, with PolarFire
> SoC; list the STM32MP1 and STM32MP2 for ST; add Analog Devices,
> Canaan Kendryte K230, StarFive JH7110 and Espressif ESP32-S31.
>
> Changes v1 -> v2:
> - link the Rockchip Linux SDK to an official Rockchip document, the
> RK3399 Linux Buildroot development guide, instead of the Khadas
> documentation. The link points to the Web Archive copy, since
> opensource.rock-chips.com is not reachable anymore.
>
> docs/website/showcase.html | 340 +++++++++++++++++++++++++++++++++++++
> 1 file changed, 340 insertions(+)
> create mode 100644 docs/website/showcase.html
>
> diff --git a/docs/website/showcase.html b/docs/website/showcase.html
> new file mode 100644
> index 0000000000..a1b8d827af
> --- /dev/null
> +++ b/docs/website/showcase.html
> @@ -0,0 +1,340 @@
> +<!--#include file="header.html" -->
> +
> +<div class="bg-primary py-5">
> +<div class="container">
> +<div class="row justify-content-center">
> +<div class="col-xxl-10 text-center">
> + <h1 class="display-4 fw-bold text-white">Powered by Buildroot</h1>
> + <p class="fs-4 fw-light text-white-50 mb-0">From cars and smart homes
> to cameras
Here, the "text-white-50" makes this line hardly readable
for me. Would it be possible to change it just to "text-white"
in order to have to a bit more contrast?
> + and retro consoles: products and projects whose operating system is
> built with
> + Buildroot.</p>
> +</div>
> +</div>
> +</div><!-- /container -->
> +</div>
[...]
> +
> + <!-- Famous projects -->
In the popular project list, we could also mention the Godot
game engine, which uses Buildroot as its build system.
https://github.com/godotengine/buildroot
Also mentioned in:
https://docs.godotengine.org/en/stable/about/list_of_features.html
> + <div class="card my-5">
> + <div class="card-header text-bg-primary rounded-top fs-5">
> + <span class="bi bi-people-fill"></span> Famous projects</div>
> + <div class="card-body p-4">
> + <div class="row row-cols-1 row-cols-md-2 row-cols-lg-3 g-3">
> +
> + <div class="col"><div class="card h-100"><div class="card-body">
> + <h4 class="mb-1"><span class="bi bi-controller
> text-primary"></span>
> + <a href="https://batocera.org">Batocera.linux</a></h4>
> + <p class="small text-body-secondary mb-2">Retro gaming</p>
> + <p class="mb-0">Plug-and-play retro gaming OS for PCs, single board
> + computers and handhelds.</p>
> + </div></div></div>
> +
> + <div class="col"><div class="card h-100"><div class="card-body">
> + <h4 class="mb-1"><span class="bi bi-joystick text-primary"></span>
> + <a href="https://www.recalbox.com">Recalbox</a></h4>
> + <p class="small text-body-secondary mb-2">Retro gaming</p>
> + <p class="mb-0">Retro gaming distribution for single board
> + computers and PCs.</p>
> + </div></div></div>
> +
> + <div class="col"><div class="card h-100"><div class="card-body">
> + <h4 class="mb-1"><span class="bi bi-camera-fill
> text-primary"></span>
> + <a href="https://openipc.org">OpenIPC</a></h4>
> + <p class="small text-body-secondary mb-2">IP cameras</p>
> + <p class="mb-0">Open firmware for IP cameras on HiSilicon, Ingenic,
> + SigmaStar, Novatek, Ambarella and more.</p>
> + </div></div></div>
> +
> + <div class="col"><div class="card h-100"><div class="card-body">
> + <h4 class="mb-1"><span class="bi bi-camera-video-fill
> text-primary"></span>
> + <a
> href="https://github.com/themactep/thingino-firmware">Thingino</a></h4>
> + <p class="small text-body-secondary mb-2">IP cameras</p>
> + <p class="mb-0">Open firmware for cameras based on Ingenic
> SoCs.</p>
> + </div></div></div>
> +
> + <div class="col"><div class="card h-100"><div class="card-body">
> + <h4 class="mb-1"><span class="bi bi-boxes text-primary"></span>
> + <a
> href="https://github.com/kubernetes/minikube/tree/master/deploy/iso/minikube-iso">minikube</a></h4>
> + <p class="small text-body-secondary mb-2">Kubernetes
> development</p>
> + <p class="mb-0">Virtual machine image for local Kubernetes
> clusters,
> + with its own br2-external tree.</p>
> + </div></div></div>
> +
> + <div class="col"><div class="card h-100"><div class="card-body">
> + <h4 class="mb-1"><span class="bi bi-droplet-fill
> text-primary"></span>
> + <a href="https://nerves-project.org">Nerves</a></h4>
> + <p class="small text-body-secondary mb-2">Elixir embedded
> framework</p>
> + <p class="mb-0">Elixir and Erlang firmware on top of a Buildroot
> + base system, <code>nerves_system_br</code>.</p>
> + </div></div></div>
> +
> + <div class="col"><div class="card h-100"><div class="card-body">
> + <h4 class="mb-1"><span class="bi bi-shield-lock-fill
> text-primary"></span>
> + <a href="https://github.com/SeedSigner/seedsigner-os">SeedSigner
> OS</a></h4>
> + <p class="small text-body-secondary mb-2">Bitcoin signing
> device</p>
> + <p class="mb-0">Minimal OS of the air-gapped SeedSigner hardware
> wallet.</p>
> + </div></div></div>
> +
> + <div class="col"><div class="card h-100"><div class="card-body">
> + <h4 class="mb-1"><span class="bi bi-layers-fill
> text-primary"></span>
> + <a href="https://github.com/skiffos/SkiffOS">SkiffOS</a></h4>
> + <p class="small text-body-secondary mb-2">Configuration layers</p>
> + <p class="mb-0">Layered Buildroot configurations for more than 50
> + targets, from the Raspberry Pi to the PinePhone.</p>
> + </div></div></div>
> +
> + <div class="col"><div class="card h-100"><div class="card-body">
> + <h4 class="mb-1"><span class="bi bi-router-fill
> text-primary"></span>
> + <a href="https://github.com/tomato64/tomato64">Tomato64</a></h4>
> + <p class="small text-body-secondary mb-2">Router firmware</p>
> + <p class="mb-0">Port of the Tomato router firmware to x86_64 and
> + arm64, on a br2-external tree.</p>
> + </div></div></div>
> +
> + </div><!-- /row -->
> + </div>
> + </div>
> +
> + <!-- Vendor SDKs -->
In the vendor SDKs, we could mention the AMD / Xilinx SoC support:
https://xilinx-wiki.atlassian.net/wiki/spaces/A/pages/2804187327/Buildroot
While the page says it is not an official support, Neal Frager
from AMD is doing a great job maintaining the defconfigs for
those boards.
> + <div class="card my-5">
> + <div class="card-header text-bg-primary rounded-top fs-5">
> + <span class="bi bi-cpu-fill"></span> Vendor SDKs</div>
> + <div class="card-body p-4">
> + <p class="text-body-secondary">Silicon and board vendors ship
> Buildroot in
> + their SDKs, so countless devices run it without saying so.</p>
> + <div class="list-group list-group-flush">
> + <a class="list-group-item list-group-item-action d-flex gap-3 py-3"
> +
> href="https://software-dl.ti.com/processor-sdk-linux/esd/AM62X/12_01_00_05_03_Buildroot/exports/docs/buildroot/Overview.html">
> + <span class="bi bi-motherboard-fill fs-3 text-primary"></span>
> + <span><b>Texas Instruments Processor SDK</b><br>
> + <span class="text-body-secondary">Official Buildroot flavour for
> AM62x and
> + AM62Lx, with the TI external tree.</span></span>
> + </a>
> + <a class="list-group-item list-group-item-action d-flex gap-3 py-3"
> +
> href="https://github.com/linux4microchip/buildroot-external-microchip">
> + <span class="bi bi-motherboard-fill fs-3 text-primary"></span>
> + <span><b>Microchip</b><br>
> + <span class="text-body-secondary">Buildroot external tree for the
> SAMA5, SAMA7, SAM9
> + and PolarFire SoC families.</span></span>
> + </a>
> + <a class="list-group-item list-group-item-action d-flex gap-3 py-3"
> + href="https://github.com/bootlin/buildroot-external-st">
> + <span class="bi bi-motherboard-fill fs-3 text-primary"></span>
> + <span><b>STMicroelectronics</b><br>
> + <span class="text-body-secondary">Buildroot external tree for the
> STM32MP1 and STM32MP2
> + boards, maintained by Bootlin.</span></span>
> + </a>
> + <a class="list-group-item list-group-item-action d-flex gap-3 py-3"
> + href="https://github.com/analogdevicesinc/br2-external">
> + <span class="bi bi-motherboard-fill fs-3 text-primary"></span>
> + <span><b>Analog Devices</b><br>
> + <span class="text-body-secondary">Buildroot external tree for the
> ADSP-SC5xx processors and
> + the ADI boards based on AMD Xilinx SoCs.</span></span>
> + </a>
> + <a class="list-group-item list-group-item-action d-flex gap-3 py-3"
> + href="https://github.com/kendryte/k230_linux_sdk">
> + <span class="bi bi-motherboard-fill fs-3 text-primary"></span>
> + <span><b>Canaan Kendryte K230</b><br>
> + <span class="text-body-secondary">Buildroot based Linux SDK for
> the K230 RISC-V AI SoC.</span></span>
> + </a>
> + <a class="list-group-item list-group-item-action d-flex gap-3 py-3"
> + href="https://github.com/starfive-tech/VisionFive2">
> + <span class="bi bi-motherboard-fill fs-3 text-primary"></span>
> + <span><b>StarFive JH7110</b><br>
> + <span class="text-body-secondary">VisionFive 2 SDK, with Buildroot
> for the root
> + filesystem.</span></span>
> + </a>
> + <a class="list-group-item list-group-item-action d-flex gap-3 py-3"
> + href="https://github.com/espressif/esp-buildroot-external">
> + <span class="bi bi-motherboard-fill fs-3 text-primary"></span>
> + <span><b>Espressif ESP32-S31</b><br>
> + <span class="text-body-secondary">Buildroot external tree for
> Linux on the ESP32-S31,
> + as a developer preview.</span></span>
> + </a>
> + </div>
> + </div>
> + </div>
> +
> + <div class="row my-5 text-center">
> + <div class="col-lg-8 offset-lg-2">
> + <h1 class="fw-light">Your product here?</h1>
> + <h3 class="text-body-secondary">Tell us about it on the
> + <a href="support.html">mailing list</a>.</h3>
> + </div>
> + </div>
> + <hr>
> +
> +</div>
> +</div>
> +</div><!-- /container -->
> +
> +<!--#include file="footer.html" -->
> --
> 2.34.1
Best regards,
Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-11-07 14:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-05 10:24 [Buildroot] [PATCH v2 1/3] website/download: complete the git clone box Angelo Compagnucci
2026-11-05 10:24 ` [Buildroot] [PATCH v2 2/3] website: add a showcase page Angelo Compagnucci
2026-11-05 10:32 ` Thomas Petazzoni via buildroot
2026-11-05 11:38 ` Angelo Compagnucci
2026-11-05 10:24 ` [Buildroot] [PATCH v2 3/3] website: add the showcase page to the navigation bar Angelo Compagnucci
2026-11-05 17:50 ` [Buildroot] [PATCH v3 1/3] website/download: complete the git clone box Angelo Compagnucci
2026-11-05 17:50 ` [Buildroot] [PATCH v3 2/3] website: add a showcase page Angelo Compagnucci
2026-11-05 17:50 ` [Buildroot] [PATCH v3 3/3] website: add the showcase page to the navigation bar Angelo Compagnucci
2026-11-06 11:16 ` [Buildroot] [PATCH v4 1/3] website/download: complete the git clone box Angelo Compagnucci
2026-11-06 11:16 ` [Buildroot] [PATCH v4 2/3] website: add a showcase page Angelo Compagnucci
2026-11-07 14:06 ` Julien Olivain via buildroot [this message]
2026-11-06 11:16 ` [Buildroot] [PATCH v4 3/3] website: add the showcase page to the navigation bar Angelo Compagnucci
2026-11-07 15:26 ` [Buildroot] [PATCH v5 1/3] website/download: complete the git clone box Angelo Compagnucci
2026-11-07 15:26 ` [Buildroot] [PATCH v5 2/3] website: add a showcase page Angelo Compagnucci
2026-11-07 15:26 ` [Buildroot] [PATCH v5 3/3] website: add the showcase page to the navigation bar Angelo Compagnucci
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=23bd9f8e90ca12911336ca571708b3ea@free.fr \
--to=buildroot@buildroot.org \
--cc=angelo.compagnucci@gmail.com \
--cc=ju.o@free.fr \
--cc=thomas.petazzoni@bootlin.com \
/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