RTL8733BS support — SDIO transport + 8733BS (follow-up to #233)

未关闭
#234 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
28/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
技术栈
c

调研方向

Start by reading src/RtlTransport.h and the existing PCIe transport and CreateRtlDevicePcie path; the issue also depends on #233 landing first. Decide the host-side SDIO access model, then scope the new SDIO transport, CMD52/53 register access, FIFO frame transfer, and bus-specific bring-up. Done means an SDIO open/factory path supports RTL8733BS without changing the HAL.

由索引模型根据 Issue 内容生成。

描述

enhancement help wanted

Summary

Follow-up to #233 (RTL8733BU USB support). Add the SDIO sibling RTL8733BS — the bus variant used on OpenIPC camera SoCs (Ingenic/Sigmastar).

Why this is separate / larger

Once #233 lands, the 8733B HAL (halmac 87xx, phydm tables, RF/narrowband, coex) is done and bus-neutral — it holds an RtlAdapter and never touches the bus directly. The remaining work is a brand-new SDIO transport, which devourer does not have today:

  • New SdioTransport implementing devourer::IRtlTransport (src/RtlTransport.h) — register plane over SDIO CMD52/53 (byte + block IO) instead of USB vendor control; frame plane over the SDIO TX/RX FIFO.
  • is_usb() returns false; wire the SDIO-specific bring-up rows (RX agg, FIFO/queue mapping, no USB DLFW 512-pad) the way PCIe already gates its bus-specific steps.
  • Host-side SDIO access model (mmc/sdio userspace path) — the analog of "the caller owns libusb / vfio" for SDIO. Needs a design decision.
  • Factory: add an SdioTransport::Open(...) + CreateRtlDeviceSdio(...) path mirroring CreateRtlDevicePcie.

Depends on

  • #233 (8733B HAL, USB-first) merged.

Out of scope

The HAL itself — reused unchanged from #233.


The USB HAL in #233 is deliberately bus-neutral so this reduces to a transport port + host-access model.

主要语言
C
星标
56
派生
29
平均合并
3 小时 43 分钟
30 天内合并 PR
75

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

OpenIPC/devourer 的其他 Issue

查看 OpenIPC/devourer 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。