The Hunted #consim #gaming #gmtgames #solo #submarine #uboot #wargaming https://www.marcueberall.com/the-hunted/
Finally updated my U-Boot again :D
The recording of my #FOSDEM talk (~25 minutes) on Rockchip mainlining is now available! #linux #uboot
https://fosdem.org/2026/schedule/event/KLFW73-no-line-like-mainline-rockchip/
I am thrilled to be back at FOSDEM. It is a fantastic opportunity to meet with the open source community and connect with fellow developers at such a great conference!
Please join me this Saturday in the FOSS on Mobile devroom. I will be presenting the technical evolution of the Snapdragon 8 Gen 3, demonstrating how we achieved full mainline support—from power management to the Adreno GPU—running on actual product hardware.
I look forward to seeing you there.
Saturday, 18:30 | Room UB4.132
Gorki 1970 – Ein U-Boot-Reaktorunfall und seine Vertuschung
Gorki ein Zentrum des Kalten Krieges Die Stadt Gorki, heute als Nischni Nowgorod bekannt, war im sowjetischen Zeitalter ein Zentrum des militärisch-industriellen Komplexes. Als sogenannte „geschlossene Stadt“ war sie für Ausländer und unautorisierte Sowjetbürger gleichermaßen unerreichbar. Inmitten dieser geheimnisvollen Metropole, am Ufer der Wolga, befand sich die Werft 112, offiziell bekannt als die Krasnoye Sormovo Fabrik. Dieses Werk war entscheidend für den Aufbau der […]Collabora Shows How to Run Debian on the OpenWrt One Using NVMe Storage
Flashing Linux images on RK3568 made simple ⚙️
This guide shows how to flash boot.img & rootfs.img via TFTP + U-Boot on the Forlinx RK3568 dev board.
✔️ Fast network flashing
✔️ Clear eMMC partitioning
✔️ Industrial-grade reliability
✔️ Ready for AI & edge apps
https://www.forlinx.net/industrial-news/forlinx-rk3568-tftp-flash-guide-766.html
The rest of the day is dedicated to hands-on work, discussions, and collaboration on areas like kernel mainlining, bootloaders ( #uboot ), packaging for mobile distributions, and preparation for upcoming community events such as #FOSDEM2026 .
Těšíme se na všechny!
2/2
So I followed up on one ofthe other, non-UEFI, suggestions, which is to create a Linux-format kernel image and boot with `booti`. This has a simple 64-byte header, followed by binary executable data.
So I do that, and #UBoot says it can't allocate the RAM for the image. Doesn't say *why* (like I've asked for too much, or the address range I want is already used or out of range). Just that it can't.
:blobcatangry:
Some progress, I've ported those changes to the latest #uboot, will upload a working repo to gitlab soon.
Also finally worked out how to actually boot a kernel I've compiled. Ran I to an error when just using `bootm` - `FDT and ATAGS support not compiled in`, it took me a while to work out that I had to include the dtb as well.
I've now reached: `Starting kernel ...` but unsurprisingly it stops there, now need to make an actually functioning kernel. It's tricky as it's a balance of a working kernel and a working device tree, my plan was to use the one I have for u-boot as a starting point as it's very basic
So I'm now told I'm holding it wrong, and I need to boot with UEFI. Which is *>2000* ages of specification, plus a load more reading on how to configure UEFI. And UEFI isn't even mentioned in the qemu docs for the machine I'm emulating (risc-v virt), so I don't even know if it's available.
How the hell is a human being meant to be able to understand all this stuff to actually use the hardware?
I've been trying to write a very basic OS. The goal: to make the thing understandable to one person. But modern hardware and systems... *sigh*.
I'm booting with U-Boot, because I couldn't get qemu to boot the kernel directly. Now I need some information from the device tree, but booting with u-boot's `bootelf` doesn't pass the DT to the kernel it's starting.
1/2
Why do I always start a file transfer over serial at 115200 when I've balanced all the equipment on me. Got another 11mins and cannot move, but I'm too far to stop and actually get comfortable.
Finally managed to get proper serial access to u-boot on my Samsung A5 (a5y17lte) using https://github.com/dsankouski/u-boot/tree/a5y17lte/board/samsung/axy17lte
I did have to break open my last a5y17lte and add lines to the internal serial port to check as it was very hard to get it working blind.
I've actually not done anything particularly special just reused other people's work but getting my head around it was a challenge. I'll publish an image file for others if they wanted to try it out (I appreciate the a5y17lte hacking club membership currently stands at 1).
Exciting to see that #DasUBoot has joined @conservancy as a member project!
Odds are you have used (or you own) a device that boots with U-Boot. It's another reason to consider supporting Software Freedom Conservancy if you are able.
Become a Sustainer today (if you can)!
#SFC #FOSS #OSS #UBoot #Bootloader #SoftwareFreedom #Sustainable
https://sfconservancy.org/news/2025/dec/29/u-boot-has-joined-sfc/
Today, @conservancy announced #UBoot joined as a member project. Folks who watch closely know: #SFC doesn't take any #FreeSoftware project these days. When SFC started, we were just 1 of ≤ 3 #FOSS fiscal sponsors. Today, ∃ dozens of options.
In response, SFC focused its fiscal sponsorship on only the *most* important projects for the future of #SoftwareFreedom — like UBoot.
Support fiscal sponsorship for the best #copyleft projects, as an SFC Sustainer.