Qualcomm Ethernet, RMNET, and IPQ packet processor drivers
An umbrella of Qualcomm network drivers: the QCA7000 powerline-Ethernet bridge (SPI/UART, common in automotive HomePlug designs), the EMAC gigabit controller in older Snapdragon SoCs, the RMNET data path that carries IP traffic over Qualcomm cellular modems, and the PPE packet engine in current IPQ Wi-Fi router SoCs like the IPQ9574.
recommendation
It should stay because the directory covers hardware Qualcomm is still actively shipping in 2025, including the IPQ9574 router platform listed in the Dragonwing NPro 7 product brief, and git history shows ongoing development on the PPE, RMNET, EMAC, and QCA7000 subdrivers into early 2026. A prior attempt to remove related QDF24xx code was even reverted, indicating maintainers consider this family in-scope rather than legacy.
repository signals
sources
- cateee.net
LKDDb shows this directory still covers multiple in-tree Qualcomm network drivers, including QCOM_EMAC, QCOM_PPE, and QCA7000 variants, with support entries continuing through 7.0-rc+HEAD.
- cateee.net
LKDDb lists CONFIG_QCOM_PPE for Qualcomm IPQ SoCs and specifically matches qcom,ipq9574-ppe, indicating current hardware coverage rather than legacy-only support.
- cateee.net
LKDDb shows CONFIG_RMNET remains present through current kernel series and describes an embedded data-path use case, supporting ongoing deployment in Qualcomm modem-based systems.
- docs.qualcomm.com
Qualcomm's 2025 Dragonwing NPro 7 product brief still lists IPQ9574 as an ordering part number, showing at least one chipset served by this directory is still an actively marketed platform in 2025.
codex reasoning notes (technical)
Shell inspection of local Kconfig/files confirmed this is an umbrella driver directory with active subdrivers (QCA7000 SPI/UART, EMAC, RMNET, PPE). Local `git log` showed substantive commits through 2026-04-03, including new PPE/IPQ9574 work and bug fixes across qca_spi, rmnet, emac, and qca_uart; no removal series was found, and a prior QDF24xx removal was reverted, which argues against deprecation. URLs were obtained via web search (LKDDb and Qualcomm product brief). Lore-specific tooling was unavailable in this session (`lei` missing; web lore queries returned no usable hits), so upstream activity was assessed from local git history instead.