<\/span><\/h2>\nThe primary technical justification for the removal of Baikal support centers on the lack of active maintenance. In the world of the Linux kernel, code that is not actively maintained by a designated individual or organization is often viewed as "dead weight," posing potential security risks and increasing the burden on core maintainers to ensure compatibility with evolving kernel subsystems. For several years, the bulk of Baikal\u2019s kernel support was contributed by Serge Semin, a prolific developer who served as the primary link between Baikal Electronics and the upstream Linux community.<\/p>\nHowever, the maintenance landscape shifted dramatically in late 2024. Following a series of policy adjustments regarding compliance and international sanctions, approximately a dozen Russian developers, including Serge Semin, were removed from the official Linux kernel MAINTAINERS file. This move was described by senior kernel maintainers, including Greg Kroah-Hartman and Linus Torvalds, as a necessary step to comply with various legal requirements and "compliance rules." Without Semin or a sanctioned alternative to oversee the Baikal code, the drivers became stagnant.<\/p>\n
The Linux kernel community operates on a "use it or lose it" philosophy. Because Baikal hardware is exceptionally rare outside of specific Russian state sectors and is virtually impossible to acquire in the West due to trade restrictions, there is no community of developers available to take over maintenance. Consequently, the decision to purge the code reflects a pragmatic approach to kernel hygiene, removing thousands of lines of code that serve an increasingly narrow and unreachable user base.<\/p>\n
<\/span>A History of Baikal Electronics: Ambition and Obstacles<\/span><\/h2>\nTo understand the weight of this removal, one must examine the history of Baikal Electronics. Founded in January 2012, Baikal Electronics emerged as a spinoff of T-Platforms, a Russian firm renowned for its work in the supercomputing sector. The company was envisioned as a cornerstone of Russia\u2019s "import substitution" strategy, an effort to reduce the nation’s reliance on Western technology from giants like Intel and AMD.<\/p>\nThe company’s technical journey was diverse:<\/p>\n
\nThe MIPS Era:<\/strong> Early efforts focused on the Baikal-T1, a dual-core processor based on the MIPS P5600 architecture. It was designed primarily for networking equipment, industrial automation, and embedded systems.<\/li>\nThe ARM Transition:<\/strong> Seeking higher performance and a broader ecosystem, Baikal pivoted to ARM architecture. The Baikal-M (Cortex-A57) was intended for workstations and thin clients, while the Baikal-S (Cortex-A75) was designed for server-grade applications.<\/li>\nManufacturing Realities:<\/strong> Despite being Russian-designed, the chips relied on global supply chains. The processors were manufactured using advanced process nodes at TSMC (Taiwan Semiconductor Manufacturing Company).<\/li>\n<\/ul>\nThe strategy appeared successful for a time, with Baikal processors finding homes in domestic PC brands and government infrastructure. However, the geopolitical events of 2022 fundamentally altered the company’s trajectory.<\/p>\n
<\/span>The Impact of Geopolitical Tensions and Sanctions<\/span><\/h2>\nThe 2022 Russian invasion of Ukraine triggered a cascade of international sanctions that crippled the Russian semiconductor industry. For Baikal Electronics, the consequences were immediate and devastating. TSMC, adhering to international trade restrictions, ceased all manufacturing for Russian entities. This move effectively orphaned the Baikal-M and Baikal-S designs, as Russia lacks domestic foundries capable of producing chips at the 28nm or 16nm nodes required for these processors.<\/p>\nFurthermore, approximately 150,000 Baikal-M units that had already been manufactured were reportedly seized or blocked in Taiwan. The loss of access to ARM\u2019s intellectual property licenses further complicated the development of future iterations. These pressures led Baikal Electronics to file for bankruptcy in August 2023. Although the company underwent restructuring and attempted to pivot toward RISC-V\u2014an open-standard instruction set architecture\u2014the damage to its mainstream ARM-based lineup was irreversible.<\/p>\n
While Baikal claimed to have shipped a total of 85,000 processors since its inception and recently announced the serial production of the Baikal-U1000 RISC-V microcontroller in late 2025, these numbers are marginal compared to the global semiconductor market. The shift to RISC-V represents a "reset" for the company, but it does nothing to save the legacy ARM and MIPS code currently being purged from the Linux kernel.<\/p>\n
<\/span>Technical Implications for Existing Users<\/span><\/h2>\nThe removal of Baikal support from the mainline Linux kernel creates a "version ceiling" for users currently operating Baikal-based hardware. Because the code is being stripped in the Linux 7.1 cycle, any future security patches, performance optimizations, or new features introduced in subsequent kernel versions will be unavailable to these systems unless the owners maintain their own out-of-tree kernel patches.<\/p>\nIndustry analysts suggest that users of Baikal-T, Baikal-M, and Baikal-S hardware will be forced to remain on Linux 6.18 Long-Term Support (LTS) or earlier versions. While LTS kernels receive maintenance for several years, they eventually reach end-of-life (EOL). For Russian state enterprises that deployed these CPUs as a security measure to ensure "sovereign" computing, the loss of mainline Linux support creates a paradox: the hardware intended to provide independence now requires a fragmented and isolated software stack to remain functional.<\/p>\n
<\/span>Timeline of Baikal\u2019s Integration and Exit<\/span><\/h2>\nThe rise and fall of Baikal support in the Linux kernel can be traced through several key milestones:<\/p>\n
\n2012:<\/strong> Baikal Electronics is founded.<\/li>\n2014-2015:<\/strong> Initial MIPS-based Baikal-T1 support is mainlined into the Linux kernel.<\/li>\n2019-2021:<\/strong> Expansion of support for Baikal-M (ARM) begins, with significant contributions to the Device Tree and subsystem drivers.<\/li>\nFebruary 2022:<\/strong> Global sanctions halt TSMC production and ARM licensing for Baikal.<\/li>\nAugust 2023:<\/strong> Baikal Electronics files for bankruptcy amid supply chain collapse.<\/li>\nOctober 2024:<\/strong> Major purge of Russian maintainers from the Linux kernel, including primary Baikal contributor Serge Semin.<\/li>\nApril 2026:<\/strong> Linus Torvalds merges the removal of Baikal-specific ATA and SoC code in the Linux 7.1-rc1 release.<\/li>\n<\/ul>\n<\/span>Broader Implications for Open Source Neutrality<\/span><\/h2>\nThe removal of Baikal support is more than a technical cleanup; it is a reflection of the fracturing of the global technology landscape. For decades, the Linux kernel was viewed as a neutral territory where developers from all nations could collaborate regardless of the political climate. The 2024 maintainer removals and the subsequent code purges suggest that this era of perceived neutrality is evolving into one of regulatory compliance.<\/p>\nFrom a development perspective, the Linux kernel community is increasingly prioritizing "sustainable maintenance." If a hardware platform cannot guarantee a long-term maintainer who can participate in the community without legal or logistical hurdles, that platform becomes a liability. The Baikal case serves as a warning for other regional hardware projects: without a diverse, international base of contributors and a stable manufacturing chain, mainline support is never guaranteed.<\/p>\n
<\/span>Conclusion and Future Outlook<\/span><\/h2>\nThe removal of Baikal CPU support from the Linux kernel marks the end of an ambitious chapter in Russian domestic computing. What began as a mission to create a self-sufficient hardware ecosystem has succumbed to the pressures of international sanctions and the rigorous maintenance standards of the open-source community. While Baikal Electronics continues to explore the RISC-V architecture as a path forward, any future support for such chips in the Linux kernel will likely face extreme scrutiny and must navigate a complex landscape of international compliance.<\/p>\n
For the broader tech industry, the "de-Baikalization" of the kernel underscores the importance of supply chain resilience and the deep interconnectedness of hardware and software. As the Linux kernel moves forward into the 7.x series, it does so with a leaner codebase, having shed the remnants of a project that, while technically sound in its design, could not survive the geopolitical storms of the 2020s.<\/p>\n","protected":false},"excerpt":{"rendered":"
The Linux kernel has officially begun the process of removing support for the Baikal line of Russian-designed processors, marking a significant turning point in the relationship between the global open-source community and Russian hardware initiatives. This decision, manifesting in the Linux 7.1 development cycle, involves the systematic stripping of driver code and device tree bindings …<\/p>\n","protected":false},"author":25,"featured_media":5407,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[203],"tags":[810,808,814,809,807,811,33,806,205,813,206,204,569,812,284],"newstopic":[],"class_list":["post-5408","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-open-source","tag-amid","tag-baikal","tag-challenges","tag-cpus","tag-ends","tag-geopolitical","tag-github","tag-kernel","tag-linux","tag-maintenance","tag-open-source","tag-oss","tag-russian","tag-shifts","tag-support"],"_links":{"self":[{"href":"https:\/\/codeguilds.com\/index.php?rest_route=\/wp\/v2\/posts\/5408","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/codeguilds.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/codeguilds.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/codeguilds.com\/index.php?rest_route=\/wp\/v2\/users\/25"}],"replies":[{"embeddable":true,"href":"https:\/\/codeguilds.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=5408"}],"version-history":[{"count":0,"href":"https:\/\/codeguilds.com\/index.php?rest_route=\/wp\/v2\/posts\/5408\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/codeguilds.com\/index.php?rest_route=\/wp\/v2\/media\/5407"}],"wp:attachment":[{"href":"https:\/\/codeguilds.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=5408"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/codeguilds.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=5408"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/codeguilds.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=5408"},{"taxonomy":"newstopic","embeddable":true,"href":"https:\/\/codeguilds.com\/index.php?rest_route=%2Fwp%2Fv2%2Fnewstopic&post=5408"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}