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

Open
#234 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
28/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
c

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
C
Stars
56
Forks
29
Avg merge
3h 43m
Merged PRs (30d)
75

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenIPC/devourer

All issues in OpenIPC/devourer

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.