<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://angolini.github.io/</id><title>Angolini's Blog</title><subtitle>A blog with technical writing about Yocto, Notion, and Linux.</subtitle> <updated>2026-03-17T19:28:53-03:00</updated> <author> <name>Daiane Angolini</name> <uri>https://angolini.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://angolini.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://angolini.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Daiane Angolini </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>bitbake-setup: New Terminology</title><link href="https://angolini.github.io/posts/bitbake-setup-New-Terminology/" rel="alternate" type="text/html" title="bitbake-setup: New Terminology" /><published>2026-02-09T21:00:00-03:00</published> <updated>2026-03-17T19:05:31-03:00</updated> <id>https://angolini.github.io/posts/bitbake-setup-New-Terminology/</id> <content type="text/html" src="https://angolini.github.io/posts/bitbake-setup-New-Terminology/" /> <author> <name>Daiane Angolini</name> </author> <summary>Overview With the introduction of bitbake-setup, the Yocto Project brings a set of new terms that are important to understand before diving into the tool. These terms are documented in the BitBake User Manual - Environment Setup chapter. Term What it is Related settings Top Directory The workspace root, by default it’s bitbake-builds ...</summary> </entry> <entry><title>bitbake-setup: Preparing for Wrynose</title><link href="https://angolini.github.io/posts/bitbake-setup-Preparing-for-Wrynose/" rel="alternate" type="text/html" title="bitbake-setup: Preparing for Wrynose" /><published>2026-02-01T21:00:00-03:00</published> <updated>2026-03-17T19:05:31-03:00</updated> <id>https://angolini.github.io/posts/bitbake-setup-Preparing-for-Wrynose/</id> <content type="text/html" src="https://angolini.github.io/posts/bitbake-setup-Preparing-for-Wrynose/" /> <author> <name>Daiane Angolini</name> </author> <summary>Introduction bitbake-setup has been around since YP 5.3 (Whinlatter). Although it is still under development, the goal is to have a tool to automate the initialization and management of Yocto Project build environments, and of course, a way to better share local configurations. Let’s see the main changes that bitbake-setup will bring to Yocto Project 6.0 (Wrynose). New Scripts Basically: ...</summary> </entry> <entry><title>Bitbake-setup: Common Questions and Answers</title><link href="https://angolini.github.io/posts/Bitbake-setup-Common-Questions-and-Answers/" rel="alternate" type="text/html" title="Bitbake-setup: Common Questions and Answers" /><published>2025-12-28T21:00:00-03:00</published> <updated>2026-03-17T19:05:31-03:00</updated> <id>https://angolini.github.io/posts/Bitbake-setup-Common-Questions-and-Answers/</id> <content type="text/html" src="https://angolini.github.io/posts/Bitbake-setup-Common-Questions-and-Answers/" /> <author> <name>Daiane Angolini</name> </author> <summary>Introduction A list of common questions I had when I started learning about bitbake-setup. 1. BitBake Clone Strategy Question: Am I downloading BitBake to download BitBake? Answer: Yes! The bitbake-setup you use to init a Setup is different from the BitBake cloned inside the Setup. You can have one copy of BitBake to init all your Setups. But the BitBake from your project will probably b...</summary> </entry> <entry><title>How to update dtb or Image when booting lmp-base</title><link href="https://angolini.github.io/posts/How-to-update-dtb-or-Image-when-booting-lmp-base/" rel="alternate" type="text/html" title="How to update dtb or Image when booting lmp-base" /><published>2024-08-11T21:00:00-03:00</published> <updated>2024-08-11T21:00:00-03:00</updated> <id>https://angolini.github.io/posts/How-to-update-dtb-or-Image-when-booting-lmp-base/</id> <content type="text/html" src="https://angolini.github.io/posts/How-to-update-dtb-or-Image-when-booting-lmp-base/" /> <author> <name>Daiane Angolini</name> </author> <summary>The first step is to enable (or review if this is already enabled) the UMS fragment into the U-Boot configuration. Reference: https://docs.foundries.io/latest/porting-guide/pg-spl-uboot-fragments.html#creating-the-u-boot-configuration-fragments The fragment to be added: CONFIG_CMD_USB_MASS_STORAGE=y After that, rebuild the image, reflash to the board. Booting the board, stop at U-Boot prom...</summary> </entry> <entry><title>Git send-email using --in-reply-to to send a Tested-by message only</title><link href="https://angolini.github.io/posts/Git-send-email-using-in-reply-to-to-send-a-Tested-by-message-only/" rel="alternate" type="text/html" title="Git send-email using --in-reply-to to send a Tested-by message only" /><published>2024-08-02T08:13:00-03:00</published> <updated>2024-08-02T08:13:00-03:00</updated> <id>https://angolini.github.io/posts/Git-send-email-using-in-reply-to-to-send-a-Tested-by-message-only/</id> <content type="text/html" src="https://angolini.github.io/posts/Git-send-email-using-in-reply-to-to-send-a-Tested-by-message-only/" /> <author> <name>Daiane Angolini</name> </author> <summary>Ok, it’s easy to find the command line to use when you have the patch you want to reply --in-reply-to, but I was struggling to understand what I was supposed to add to the /path/to/YOUR_REPLY to style it properly. As it was not an answer, it was a Tested-by tag. And all the top-posting thing. This post helped me to understand. https://paldan.altervista.org/kernel-mailing-list-replies-for-l...</summary> </entry> </feed>
