l4-hackers

Download

l4-hackers@os.inf.tu-dresden.de

February 2026

2 participants
2 discussions

Mounting the Sd card on the L4re for Imx 95.
by Marka Sriharsha 08 Feb '26

08 Feb '26

The L4Re version I am using is r-2025-W48. Initially, I attempted to boot using the initramfs-based method. In this approach, I converted the uImage into a raw bin image, because loading the uImage directly resulted in a Bad kernel image error, likely due to the default uImage header handling. After flashing the converted binary to the SD card, the system booted but consistently got stuck during early boot. Even when different load addresses are specified in U-Boot, the kernel is always relocated to a fixed address (0x90080000). This address overlaps with a reserved memory region (e.g., vpu_boot@a0000000), leading to a region overlap error and reboot. I'm attracting the log (Initramfs.txt). After this, I switched to the SD card hardware passthrough method. Following the i.MX documentation, I prepared the SD card as follows: Partition 1: FAT partition containing bootstrap.uimage and the i.MX95 device tree Partition 2: Root filesystem As suggested, I updated the configuration (.cfg) file by following the tutorial, and this resolved the console misconfiguration issue. The system now boots correctly, and I am able to see the console output. For reference, I am attaching the boot logs(Boot_partition_2.txt) Although the system boots successfully, the SD card root partition is not being detected or mounted. While following the documented steps to enable SD card access, the boot process ends with a “no device found” error for the SD card. After further debugging, I noticed that for i.MX95, there is nohw_devices.iofile available in the following repository: [https://github.com/kernkonzept/io/tree/master/io/configs] Because of this, it is unclear how the SD/MMC hardware should be described for i.MX95, and the block device does not appear during boot. For reference, I am attaching the boot logs(Boot_partition_3.txt) Is there an official hw_devices.io configuration available for i.MX95? or without the hw_device.io also we can mount the sd card? Any guidance or example configuration would be very helpful for mounting the rootfs.

2 1

Beyond the Bricks: How Google's Block Breaker Doodle Reminds Us of the Joy of Play
by blockbreakerapk10174＠gmail.com 06 Feb '26

06 Feb '26

In the relentless digital stream of our daily lives—a torrent of emails, notifications, and curated content—a moment of pure, unadulterated play can feel like a radical act. It was within this context that, on a seemingly ordinary day, millions of people worldwide were greeted by a delightful surprise on Google’s homepage: the Google Block Breaker Doodle. This wasn’t just a static logo; it was a fully playable, wonderfully crafted version of the classic arcade game, Breakout. With a click, the world’s most ubiquitous search portal transformed into a minimalist arcade, inviting users to smash a wall of colorful <a href="https://blockbreaker.ws/">google block breaker doodle</a> bricks with a bouncing pixel. The phenomenon was more than a nostalgic trip; it was a masterclass in design philosophy, a commentary on workplace culture, and a potent reminder of a fundamental human need. The genius of the Google Block Breaker Doodle lay in its elegant simplicity and its deep-rooted heritage. The original Breakout, released by Atari in 1976, is itself a piece of tech legend. It was a direct descendant of Pong, emphasizing solitary focus and rhythmic precision. More intriguingly, its original development involved a young Steve Jobs and Steve Wozniak, who were tasked with creating its circuit board. For Google to choose this game was a wink to its own Silicon Valley lineage, connecting the dots from the garage-built ethos of early computing to the sleek, global platform of today. The Doodle didn’t just reference a game; it honored a foundational moment in digital interactivity. But the impact went far beyond history. The user experience was perfectly calibrated. The mechanics were instantly understandable: move the paddle, bounce the ball, break the blocks. There were no tutorials, no loot boxes, no complex narratives. The objective was clear, the feedback immediate (the satisfying disappearance of a brick), and the failure state gentle—a chance to try again instantly. This created a state of "flow," that psychological condition of complete immersion and focused enjoyment. In a world of endless scrolling and multitasking, the Google Block Breaker Doodle offered a rare commodity: a single, simple task that commanded full attention. It was a digital mindfulness exercise disguised as a game. The timing and placement of the Doodle were equally significant. By situating this portal to play on the default homepage for countless browsers, Google shattered the traditional boundary between "work" and "play." For a brief moment, the tool we use for research, communication, and productivity became a site of leisure. This wasn’t an app you had to seek out; it was presented, almost insistently, as an alternative path. It encouraged what modern productivity gurus might call a "micro-break"—a short, intentional pause to reset the brain. The message was subtle but powerful: creativity and efficiency are not antithetical to play; they are often fueled by it. The Google Block Breaker Doodle became a sanctioned, global five-minute recess, challenging the grim grind of hustle culture. Furthermore, the Doodle served as a brilliant, unspoken showcase of web technology. This was no mere Java applet from the early 2000s. It was a smooth, responsive, and visually pleasing experience built with modern web standards, demonstrating what a browser could do without any plugins or downloads. It was a testament to the sophistication of accessible web design, proving that complex interactivity could be delivered instantly and seamlessly to anyone with an internet connection. In this way, the playful facade was also a technical flex, a demonstration of Google’s core competency in making the web a more dynamic canvas. On a societal level, the Doodle created a shared cultural moment. Social media lit up with high scores, strategies, and good-natured commiseration over near-misses. Colleagues compared scores by the watercooler. It democratized a specific joy, creating a common reference point across generations. Older users relived childhood memories in arcades or on early home consoles, while younger ones discovered a genre stripped bare of modern gaming’s complexities. The Google Block Breaker Doodle acted as a universal language, speaking through the simple verbs of aim, bounce, and break. Ultimately, the lasting lesson of the Google Block Breaker Doodle is about the enduring human need for purposeless purpose. We are wired to derive satisfaction from mastering simple systems, from seeing a clear cause and effect, and from engaging in activities where the only goal is the activity itself. In our increasingly optimized and outcome-driven lives, we often engineer this joy out of existence. The Doodle was a gentle intervention, a reminder that play is not frivolous. It is essential for cognitive maintenance, sparking joy, relieving stress, and fostering a creative mindset. Google, a company built on algorithms and data, used its most prized real estate to advocate for something beautifully analog in spirit: the click of a mouse, the bounce of a ball, the shattering of a digital wall. The Google Block Breaker Doodle was more than a clever homage; it was a manifesto in interactive form. It argued that within the cold architecture of code and connectivity, there must always be room for a paddle, a ball, and a wall of bricks waiting to be broken. It reminded us that sometimes, the most productive thing we can do is to simply play.

1 0