NetHub：修订间差异
跳转到导航
跳转到搜索
小 Sync NetHub docs from local Markdown (2026-04-24 wording update) |
小 Unify tone and terminology across NetHub docs (2026-04-24) |
||
| 第1行： | 第1行： | ||
= NetHub = | = NetHub = | ||
NetHub bridges device-side Wi-Fi capability to a selected host | NetHub bridges device-side Wi-Fi capability to a selected host interface. | ||
The current solution targets Wi-Fi SoCs such as <code>BL616 / BL618 / BL616CL / BL618DG</code>. | The current solution targets Wi-Fi SoCs such as <code>BL616 / BL618 / BL616CL / BL618DG</code>. | ||
| 第36行： | 第36行： | ||
| [[NetHubQuickBringup|NetHubQuickBringup.md]] || default interface, main configuration switches, build and flash, SDIO and USB pins | | [[NetHubQuickBringup|NetHubQuickBringup.md]] || default interface, main configuration switches, build and flash, SDIO and USB pins | ||
|- | |- | ||
| [[NetHubArchitecture|NetHubArchitecture.md]] || internal layering, public APIs, support matrix, and | | [[NetHubArchitecture|NetHubArchitecture.md]] || internal layering, public APIs, support matrix, and interface differences | ||
|- | |- | ||
| [[NetHubVirtualChannel|NetHubVirtualChannel.md]] || USER virtual channel scope, prerequisites, APIs, and limits | | [[NetHubVirtualChannel|NetHubVirtualChannel.md]] || USER virtual channel scope, prerequisites, APIs, and limits | ||
| 第43行： | 第43行： | ||
== Key Points == | == Key Points == | ||
* <code>SDIO</code> is the current default interface | * <code>SDIO</code> is the current default interface for the in-tree bring-up path. | ||
* <code>USB</code> device-side backend is implemented with <code>ECM + ACM</code>. | * <code>USB</code> device-side backend is implemented with <code>ECM + ACM</code>. | ||
* <code>SPI</code> is still a stub and is not ready for bring-up. | * <code>SPI</code> is still a stub and is not ready for bring-up. | ||
* <code>nethub</code> core exposes data-path, control | * <code>nethub</code> core exposes data-path, control path, and virtual channel facades without directly depending on <code>ATModule</code>. | ||
* The optional <code>ATModule + bflbwifid + bflbwifictrl</code> flow is available, but | * The optional <code>ATModule + bflbwifid + bflbwifictrl</code> flow is available, but not mandatory. | ||
== In-Repo Reference Directories == | == In-Repo Reference Directories == | ||
2026年4月24日 (五) 14:27的最新版本
NetHub
NetHub bridges device-side Wi-Fi capability to a selected host interface.
The current solution targets Wi-Fi SoCs such as BL616 / BL618 / BL616CL / BL618DG.
Current Status
| Item | Current status |
|---|---|
| Default interface | SDIO
|
| USB data-path | device-side USB ECM backend implemented
|
| USB control transport | device-side USB ACM transport plumbing implemented
|
| SPI | not implemented |
| USER virtual channel | default interface is SDIO
|
| Low power | currently BL618DG only
|
| Optional ATModule control solution | available, but not mandatory |
Document Guide
Use these documents according to what you need:
| Document | Focus |
|---|---|
| NetHubQuickBringup.md | default interface, main configuration switches, build and flash, SDIO and USB pins |
| NetHubArchitecture.md | internal layering, public APIs, support matrix, and interface differences |
| NetHubVirtualChannel.md | USER virtual channel scope, prerequisites, APIs, and limits |
Key Points
SDIOis the current default interface for the in-tree bring-up path.USBdevice-side backend is implemented withECM + ACM.SPIis still a stub and is not ready for bring-up.nethubcore exposes data-path, control path, and virtual channel facades without directly depending onATModule.- The optional
ATModule + bflbwifid + bflbwifictrlflow is available, but not mandatory.
In-Repo Reference Directories
examples/wifi/nethubcomponents/net/nethubbsp/common/msg_router/linux_host/userspace/nethub
Local Documentation Source
The in-repo documentation source is:
examples/wifi/nethub/docs/