This blog post details the process of emulating an iPhone 11 running iOS 14.4.2 using QEMU, specifically highlighting the complexities involved. The author explains the necessity of using a pre-built kernel and device tree, obtained through a jailbreak, and emphasizes that building these components from source is not currently feasible. The post walks through setting up the necessary files, including the kernel, device tree, ramdisk, and a signed IPSW, and configuring QEMU for ARM virtualization. While the emulation achieves a basic boot, the author acknowledges significant limitations, such as lack of GPU acceleration, networking, and a functional touchscreen, ultimately rendering the emulated environment impractical for general use but potentially useful for low-level debugging or research.
RPCEmu emulates Risc PC systems, including the A7000 and various StrongARM-based machines. It accurately recreates the hardware of these Acorn computers, allowing users to run original RISC OS software, including applications, games, and the desktop environment itself. The emulator boasts high compatibility and performance, supporting features like ARMv3, ARMv4, and StrongARM CPUs, FPA math co-processor, VIDC1 and VIDC20 graphics, and various sound and networking devices. RPCEmu aims for complete hardware accuracy, making it a valuable tool for preserving and experiencing these classic Acorn systems.
Hacker News users expressed significant enthusiasm for RPCEmu, praising its accuracy and the developer's dedication. Several commenters reminisced about using Acorn machines, particularly the Archimedes, sharing personal anecdotes and highlighting the platform's unique RISC OS. Some discussed the technical challenges of emulating older hardware and software, while others inquired about specific features like networking and sound support. The positive feedback underscores the impact of RPCEmu in preserving the legacy of Acorn computers and making them accessible to a wider audience. A few users also expressed interest in contributing to the project or exploring the emulated systems for the first time.
The Raspberry Pi RP2040 microcontroller is now available as a standalone chip, the RP2350, allowing manufacturers to integrate it into their own designs. This dual-core Cortex-M0+ processor with 264KB of SRAM is offered in two package variants: a QFN-56 and a future LGA package with stacked external flash memory. The QFN-56 is available for immediate purchase, offering a cost-effective solution for diverse embedded applications. The stacked memory variant promises simplified design and reduced board space, though pricing and availability for that package are yet to be announced.
Hacker News users generally expressed excitement about the RP2350's availability and potential, particularly its low cost and the possibilities opened by the stacked memory variant. Several commenters discussed the chip's suitability for specific applications, including robotics, industrial control, and amateur radio. Some expressed skepticism about the real-world performance impact of the stacked memory, wanting to see benchmarks. Others debated the merits of the RP2350 compared to other microcontrollers like the ESP32, highlighting trade-offs in processing power, memory, and peripheral options. A few users also mentioned challenges they've faced with Raspberry Pi availability in the past, hoping this release would be smoother.
Scorpi is a new, open-source type-1 hypervisor designed specifically for macOS on Apple silicon. It aims to be a modern, lightweight, and performant alternative to existing solutions. Leveraging the virtualization capabilities of Apple silicon, Scorpi provides a minimal kernel responsible solely for virtualization while offloading other tasks to a dedicated "service VM." This approach prioritizes performance and security by reducing the hypervisor's attack surface. Scorpi also offers a flexible device model for efficient peripheral access and a streamlined user experience. While still in active development, it promises a compelling new option for running virtual machines on macOS.
HN commenters generally expressed excitement about Scorpi, praising its clean design and potential for macOS virtualization. Several highlighted the difficulty of macOS virtualization in the past and saw Scorpi as a promising new approach. Some questioned the performance compared to existing solutions like UTM, and others were curious about specific features like nested virtualization and GPU passthrough. A few commenters with virtualization experience offered technical insights, discussing the challenges of implementing certain features and suggesting potential improvements. The project's open-source nature and reliance on Apple's Hypervisor.framework were also points of interest. Overall, the comments reflected a cautiously optimistic view of Scorpi's potential to simplify and improve macOS virtualization.
Acorn Computers, born from a Cambridge-based electronics shop, evolved from early microcomputers like the System 1 to the iconic BBC Micro, fueled by a partnership with the British Broadcasting Corporation. This success spurred further development, including the ARM architecture, born from the Acorn RISC Machine project, and the Archimedes range utilizing this new processor. Despite innovative designs like the Acorn RISC PC and the Network Computer, Acorn struggled against the growing dominance of the PC market. Ultimately, Acorn transitioned into ARM Ltd, focusing solely on the increasingly successful ARM processor design, leaving behind its legacy of influential computers and its profound impact on the UK computing landscape.
Hacker News users discuss the linked history of Acorn Computers, praising its comprehensiveness and detailed technical information. Several commenters reminisce about their experiences with Acorn machines, particularly the BBC Micro and Archimedes, highlighting their role in the UK's computing history and education. Some discuss the innovative features of Acorn's RISC architecture and its influence on ARM processors. Others mention Acorn's business struggles and the eventual dominance of x86, while acknowledging the company's lasting legacy through ARM. A few users also share personal anecdotes about using Acorn machines for programming, gaming, and even running small businesses. The overall sentiment is one of nostalgia and appreciation for Acorn's contributions to the computing world.
Wokwi now offers a web-based simulator for developing and debugging embedded Rust programs. This online tool allows users to write, build, and run Rust code targeted for various microcontrollers, including the AVR ATmega328P (like the Arduino Uno) and RP2040 (Raspberry Pi Pico), directly in the browser. The simulator features peripherals like LEDs, buttons, serial output, and an integrated logic analyzer, enabling interactive hardware simulation without requiring physical hardware. Code can be compiled and flashed to the virtual microcontroller, and the simulator provides a debugging environment for stepping through code and inspecting variables. This simplifies the embedded Rust development process, making it more accessible for learning and experimentation.
HN commenters generally expressed enthusiasm for Wokwi's online embedded Rust simulator. Several praised its ease of use and accessibility, noting it lowers the barrier to entry for embedded development. Some highlighted the educational benefits, particularly for those new to Rust or embedded systems. A few pointed out the limitations of simulation compared to real hardware, but acknowledged the simulator's value for initial development and testing. The discussion also touched on potential improvements, including support for more microcontrollers and peripherals, as well as integration with other tools. Some users shared their positive experiences using Wokwi for specific projects, further reinforcing its practical usefulness.
The MacBook Air with the M2 chip boasts all-day battery life and impressive performance in a thin, fanless design. Available in four finishes, it features a stunning 13.6-inch Liquid Retina display, a 1080p FaceTime HD camera, and a powerful 8-core CPU. The M2 chip also allows for fast graphics performance, ideal for gaming and demanding applications. Configurations offer up to 24GB of unified memory and up to 2TB of SSD storage. It also includes MagSafe charging, two Thunderbolt ports, and a headphone jack.
HN commenters generally praise the new MacBook Air M4, particularly its performance and battery life. Several note the significant performance increase over the M1 and Intel-based predecessors, with some claiming it's the best value laptop on the market. A few express disappointment about the lack of a higher refresh rate display and the return of the MagSafe charging port, viewing the latter as taking up a valuable Thunderbolt port. Others question the need for the notch, though some defend it as unobtrusive. Price is a recurring theme, with many acknowledging its premium but arguing it's justified given the performance and build quality. There's also discussion around the base model's SSD performance being slower than the M1, attributed to using a single NAND chip instead of two. Despite these minor criticisms, the overall sentiment is highly positive.
Hector Martin (marcan) is stepping down as the lead of the Asahi Linux project, which focuses on bringing Linux support to Apple Silicon Macs. He cites burnout from the project's demanding nature and the toll it has taken on his personal life. While he'll continue contributing to Asahi Linux in a less central role, he's transitioning leadership to the core team, expressing confidence in their ability to continue the project's success. He emphasizes that this change is not due to any internal conflict or loss of enthusiasm for Asahi Linux, but rather a necessary step for his well-being and the project's long-term sustainability.
Hacker News commenters largely express gratitude for Hector Martin's (marcan) work on the Asahi Linux project, acknowledging the significant technical challenges involved in bringing Linux to Apple Silicon. Some lament his departure as a loss for the project, while others are optimistic about the future and the team he's built. Several discussions revolve around the complexities of reverse-engineering Apple hardware, the difficulties of maintainership, burnout, and the importance of funding for open-source projects. A few commenters speculate about Apple's role in the project's challenges, while others focus on the technical aspects of GPU drivers and kernel development. Some threads delve into the nuances of open-source licensing and the balance between hobby projects and professionally supported endeavors.
Hector Martin, the lead developer of the Asahi Linux project which brings Linux support to Apple Silicon Macs, has stepped down from his role as a Linux kernel developer. Citing burnout and frustration with the kernel development process, particularly regarding code review and the treatment of new contributors, Martin explained that maintaining both Asahi Linux and actively contributing to the kernel has become unsustainable. He intends to remain involved with Asahi Linux and will continue working on the project, but will no longer be directly involved in core kernel development or reviews. He hopes this change will allow him to focus on higher-level aspects of the project and improve the experience for other Asahi Linux developers.
Several Hacker News commenters expressed surprise and sadness at Hector Martin's resignation, acknowledging his significant contributions to the Asahi Linux project and the broader Linux community. Some speculated about the reasons behind his departure, citing burnout, frustration with kernel development processes, or potential new opportunities. Others discussed the implications for the future of Asahi Linux, with some expressing concern about the project's trajectory without Martin's leadership, while others remained optimistic about the strong community he fostered. A few commenters questioned the overall tone of Martin's resignation email, finding it overly critical of the Linux kernel community. Finally, some users shared personal anecdotes of interacting with Martin, praising his technical skills and helpfulness.
Lume is a lightweight command-line interface (CLI) tool designed specifically for managing macOS and Linux virtual machines (VMs) on Apple Silicon Macs. It simplifies the creation, control, and configuration of VMs, offering a streamlined alternative to more complex virtualization solutions. Lume aims for a user-friendly experience, focusing on essential VM operations with an intuitive command set and minimal dependencies.
HN commenters generally expressed interest in Lume, praising its lightweight nature and simple approach to managing VMs. Several users appreciated the focus on CLI usage and its speed compared to other solutions like UTM. Some questioned the choice of using Alpine Linux for the host environment and suggested alternatives like NixOS. Others pointed out potential improvements, such as better documentation and ARM support for the host itself. The project's novelty and its potential as a faster, more streamlined alternative to existing VM managers were highlighted as key strengths. Some users also expressed interest in contributing to the project.
This blog post details how to leverage the Rust standard library (std) within applications running on the NuttX Real-Time Operating System (RTOS), a common choice for embedded systems. The author demonstrates a method to link the Rust std components, specifically write() for console output, with NuttX's system calls. This allows developers to write Rust code that feels idiomatic, using familiar functions like println!(), while still targeting the resource-constrained environment of NuttX. The process involves creating a custom target specification JSON file and implementing shim functions that bridge the gap between the Rust standard library's expectations and the underlying NuttX syscalls. The result is a simplified development experience, enabling more portable and maintainable Rust code on embedded platforms.
Hacker News users discuss the challenges and advantages of using Rust with NuttX. Some express skepticism about the real-world practicality and performance benefits, particularly regarding memory usage and the overhead of Rust's safety features in embedded systems. Others highlight the potential for improved reliability and security that Rust offers, contrasting it with the inherent risks of C in such environments. The complexities of integrating Rust's memory management with NuttX's existing mechanisms are also debated, along with the potential need for careful optimization and configuration to realize Rust's benefits in resource-constrained systems. Several commenters point out that while intriguing, the project is still experimental and requires more maturation before becoming a viable option for production-level embedded development. Finally, the difficulty of porting existing NuttX drivers to Rust and the lack of a robust Rust ecosystem for embedded development are identified as potential roadblocks.
TinyZero is a lightweight, header-only C++ reinforcement learning (RL) library designed for ease of use and educational purposes. It focuses on implementing core RL algorithms like Proximal Policy Optimization (PPO), Deep Q-Network (DQN), and Advantage Actor-Critic (A2C), prioritizing clarity and simplicity over extensive features. The library leverages Eigen for linear algebra and aims to provide a readily understandable implementation for those learning about or experimenting with RL algorithms. It supports both CPU and GPU execution via optional CUDA integration and includes example environments like CartPole and Pong.
Hacker News users discussed TinyZero's impressive training speed and small model size, praising its accessibility for hobbyists and researchers with limited resources. Some questioned the benchmark comparisons, wanting more details on hardware and training methodology to ensure a fair assessment against AlphaZero. Others expressed interest in potential applications beyond Go, such as chess or shogi, and the possibility of integrating techniques from other strong Go AIs like KataGo. The project's clear code and documentation were also commended, making it easy to understand and experiment with. Several commenters shared their own experiences running TinyZero, highlighting its surprisingly good performance despite its simplicity.
This guide provides a comprehensive introduction to BCPL programming on the Raspberry Pi. It covers setting up a BCPL environment, basic syntax and data types, control flow, procedures, and input/output operations. The guide also delves into more advanced topics like separate compilation, creating libraries, and interfacing with the operating system. It includes numerous examples and exercises, making it suitable for both beginners and those with prior programming experience looking to explore BCPL. The document emphasizes BCPL's simplicity and efficiency, particularly its suitability for low-level programming tasks on resource-constrained systems like the Raspberry Pi.
HN commenters expressed interest in BCPL due to its historical significance as a predecessor to C and its influence on Go. Some recalled using BCPL in the past, highlighting its simplicity and speed, and contrasting its design with C. A few users discussed specific aspects of the document, such as the choice of Raspberry Pi and the use of pre-built binaries, while others lamented the lack of easily accessible BCPL resources today. Several pointed out the educational value of the guide, particularly for understanding compiler construction and the evolution of programming languages. Overall, the comments reflected a mix of nostalgia, curiosity, and appreciation for BCPL's role in computing history.
Qualcomm has prevailed in a significant licensing dispute with Arm. A confidential arbitration ruling affirmed Qualcomm's right to continue licensing Arm's instruction set architecture for its Nuvia-designed chips under existing agreements. This victory allows Qualcomm to proceed with its plans to incorporate these custom-designed processors into its products, potentially disrupting the server chip market. Arm had argued that the licenses were non-transferable after Qualcomm acquired Nuvia, but the arbitrator disagreed. Financial details of the ruling remain undisclosed.
Hacker News commenters largely discuss the implications of Qualcomm's legal victory over Arm. Several express concern that this decision sets a dangerous precedent, potentially allowing companies to sub-license core technology they don't fully own, stifling innovation and competition. Some speculate this could push other chip designers to RISC-V, an open-source alternative to Arm's architecture. Others question the long-term viability of Arm's business model if they cannot control their own licensing. Some commenters see this as a specific attack on Nuvia's (acquired by Qualcomm) custom core designs, with Qualcomm leveraging their market power. Finally, a few express skepticism about the reporting and suggest waiting for further details to emerge.
Summary of Comments ( 0 )
https://news.ycombinator.com/item?id=43592409
HN commenters generally praised the technical achievement of emulating iOS 14 on QEMU, calling it "impressive" and "quite a feat." Some discussed the potential for security research and malware analysis, while others speculated about the possibility of running iOS apps on other platforms, though acknowledging Apple's legal stance against this. Several commenters questioned the practicality and performance of the emulation, pointing out the slow speed and limited hardware support. One highlighted the difficulty of getting the GPU to work properly, emphasizing the complexity of fully emulating a modern mobile operating system. The legality of distributing iOS firmware was also a point of discussion.
The Hacker News post titled "Emulating an iPhone in QEMU" (https://news.ycombinator.com/item?id=43592409) has generated a moderate number of comments, discussing various aspects of iOS emulation and the linked blog post.
Several commenters express excitement and interest in the advancements of iOS emulation, noting its potential for security research, app development and testing, and general experimentation. One commenter highlights the potential for analyzing malware in a controlled environment without risking a physical device. Another anticipates the ability to run older iOS versions on newer hardware as a compelling use case. The challenge of accurately emulating specific hardware features, like the GPU, is also acknowledged.
A few commenters discuss the legal implications of such emulation, particularly concerning copyright and digital rights management (DRM). The point is raised that while emulation itself may be legal, distributing copyrighted iOS firmware is not. The difference between emulating the hardware and obtaining the software is emphasized. The potential for this technology to enable piracy is also touched upon, though countered by the argument that existing jailbreaking methods already offer similar capabilities.
Technical details of the emulation process are discussed in some comments. One comment dives into the complexities of emulating the Apple A12 system-on-a-chip (SoC) and the effort required to accurately reproduce its functionality. The role of Just-In-Time (JIT) compilation in achieving reasonable performance is also mentioned. One commenter asks clarifying questions about performance benchmarks and the blog author replies with additional context about the challenges of performance analysis in emulation.
Some comments offer alternative solutions or related projects. One commenter suggests exploring Corellium, a commercial iOS virtualization platform. Another mentions the UTM project as a potential alternative for iOS virtualization on macOS. A few commenters mention the limitations of the current state of iOS emulation, particularly regarding its performance and compatibility.
Finally, a few comments engage directly with the author of the blog post, asking clarifying questions about specific technical aspects of the emulation process or offering suggestions for future development. The author engages actively, providing further insights into the project.