How notaz/pcsx_rearmed works
Based on your provided file structure and README, this project is clearly an emulator – a fork of PCSX-ReARMed (derived from PCSX-Reloaded) that is optimized for ARM devices with specialized support for various platforms (e.g., Pandora, 3DS, WiiU, etc.). It takes advantage of multiple architectural elements such as a dynamic recompiler (MIPS to ARM), a NEON-accelerated GPU plugin, and a flexible plugin interface (PSEMU) to support audio, video, and other emulation functions.
Main Components
• Emulator Core (libpcsxcore)
• Represents the heart of the emulation logic. This is where the CPU emulation (including the new dynamic recompiler in the “new_dynarec” directory), GPU processing, and overall game state management are handled.
• Sub-components for the recompiler (MIPS→ARM, including NEON support), CPU emulation routines, and critical utility functions such as memory mapping and BIOS integration.
• Frontend Modules (frontend)
• These directories contain platform-specific adaptations and interfaces. They are responsible for handling input, rendering, and platform-specific configuration.
• Separate blocks for different target systems (e.g., “320240”, “3ds”, “pandora”, “switch”, “vita”, “wiiu”) should be drawn.
• Plugin System (plugins)
• The project uses a modular plugin architecture (PSEMU interface) to provide functionality for GPU emulation, sound (e.g., dfsound, spunull), input, and more.
• Each plugin type (GPU plugins like “gpu-gles”, “gpu_unai”, “gpu_neon”, audio plugins, etc.) should appear as separate, interacting blocks.
• Auxiliary Libraries & Dependencies
• “deps” and “include” directories house libraries that support the core and plugins (e.g., libchdr, libretro-common, lightning, lightrec, mman).
• Build & Configuration Infrastructure
• Configuration files such as Makefiles, “configure”, and CI workflows in the “.github” directory. These are not runtime components, but they illustrate the system’s build and deployment pipelines.
• Optionally, present these as supporting infrastructure that ensures cross-platform builds and continuous integration.
Relationships and Interactions
• Data Flow
• Dependency Relationships
• Configuration and Build
• Build scripts and CI pipelines as an external system related to all subcomponents. This designates how the system is maintained and deployed.
Architectural Patterns and Design Principles
• Modular Plugin Architecture
• Plugin system separation: the core emulator logic is modular and extends functionalities through interchangeable plugins.
• Multi-Platform Design
• Clearly delineate the frontend layers for different platforms; this stands as a key architectural choice, ensuring the emulator adapts to various device constraints.
• Performance-Oriented Enhancements
• Use of the dynamic recompiler and NEON GPU enhancements; these are optimized paths in the processing pipeline.
• Separation of Concerns
• Clear boundaries between the core emulation engine, platform-specific frontends, and the plugin-based subsystems.