drivers/memstick/core

Sony Memory Stick bus and block core

Core support for Sony's Memory Stick family of proprietary flash memory cards, including the bus layer that talks to host controllers and the block layer that exposes Memory Stick PRO cards as storage devices. The format was widely used in Sony cameras, camcorders, PlayStation Portable consoles, and Vaio laptops from the late 1990s until Sony pivoted to SD cards around 2010.

keep-annotate conf=0.82 deploy=low replacement=none subsystem=memstick category=storage-flash
82%

recommendation

Worth keeping but documenting as legacy hardware. The code is still receiving genuine upstream attention in 2025, including a stable backport that added a timeout to prevent hangs and ongoing treewide API cleanups, so it is not bit-rotting. However, Memory Stick is a discontinued Sony format with low real-world deployment today, mostly surviving in older cameras and camcorders, so a note flagging it as legacy would help future maintainers and packagers weigh its priority.

repository signals

6 files
4,697 source lines
42 commits, 5y
+273 / −358 lines added / removed, 5y
23 authors, 5y
monthly commits · 2021-04-21 → 2026-04-21 · 42 total · active in 23/61 months
2021 2022 2023 2024 2025 2026 2021-04: 0 commits · +0 −0 2021-05: 2 commits · +24 −14 2021-06: 2 commits · +21 −30 2021-07: 2 commits · +2 −3 2021-08: 0 commits · +0 −0 2021-09: 3 commits · +11 −3 2021-10: 0 commits · +0 −0 2021-11: 0 commits · +0 −0 2021-12: 0 commits · +0 −0 2022-01: 0 commits · +0 −0 2022-02: 3 commits · +26 −98 2022-03: 0 commits · +0 −0 2022-04: 0 commits · +0 −0 2022-05: 0 commits · +0 −0 2022-06: 5 commits · +10 −11 2022-07: 0 commits · +0 −0 2022-08: 0 commits · +0 −0 2022-09: 0 commits · +0 −0 2022-10: 0 commits · +0 −0 2022-11: 1 commit · +8 −1 2022-12: 1 commit · +72 −105 2023-01: 2 commits · +5 −3 2023-02: 0 commits · +0 −0 2023-03: 0 commits · +0 −0 2023-04: 1 commit · +4 −1 2023-05: 0 commits · +0 −0 2023-06: 0 commits · +0 −0 2023-07: 0 commits · +0 −0 2023-08: 0 commits · +0 −0 2023-09: 0 commits · +0 −0 2023-10: 0 commits · +0 −0 2023-11: 0 commits · +0 −0 2023-12: 0 commits · +0 −0 2024-01: 0 commits · +0 −0 2024-02: 4 commits · +17 −18 2024-03: 0 commits · +0 −0 2024-04: 0 commits · +0 −0 2024-05: 1 commit · +4 −4 2024-06: 0 commits · +0 −0 2024-07: 1 commit · +3 −4 2024-08: 0 commits · +0 −0 2024-09: 2 commits · +7 −7 2024-10: 0 commits · +0 −0 2024-11: 0 commits · +0 −0 2024-12: 1 commit · +2 −4 2025-01: 1 commit · +27 −19 2025-02: 0 commits · +0 −0 2025-03: 1 commit · +2 −4 2025-04: 1 commit · +2 −2 2025-05: 1 commit · +1 −1 2025-06: 0 commits · +0 −0 2025-07: 1 commit · +1 −1 2025-08: 2 commits · +6 −3 2025-09: 1 commit · +1 −2 2025-10: 0 commits · +0 −0 2025-11: 0 commits · +0 −0 2025-12: 0 commits · +0 −0 2026-01: 0 commits · +0 −0 2026-02: 3 commits · +17 −20 2026-03: 0 commits · +0 −0 2026-04: 0 commits · +0 −0

sources

  1. lore.kernel.org

    The memstick core still receives real upstream maintenance and stable backports; a 2025 fix added a timeout to prevent indefinite waiting in memstick.c.

  2. lore.kernel.org

    The Memory Stick block layer is still being touched in 2025, albeit mostly by treewide API-cleanup work rather than feature development.

  3. sony.com

    Sony still documents Memory Stick compatibility in 2025, but only as part of mixed 'Memory Stick and SD Card' compatibility guidance for cameras and camcorders.

  4. en.wikipedia.org

    Memory Stick was a Sony proprietary flash-card family whose serious ecosystem development effectively ended as Sony shifted toward SD around 2010; newer support is largely legacy or adapter-based.

codex reasoning notes (technical)

Local source inspection shows this directory is the Memory Stick bus/block stack, not just helpers. lore_file_timeline on memstick.c produced the stable backport URL and shows continued maintenance through late 2025; lore_file_timeline on mspro_block.c produced the 2025 cleanup patch URL and shows ongoing treewide churn, with no removal-series evidence found. Web search produced the Sony compatibility page and Wikipedia page; together they support a legacy-but-still-supported ecosystem with low present-day deployment, so keep the driver but annotate it as legacy rather than deprecate/remove.