NetHub:修订间差异

来自Bouffalo Lab Docs
跳转到导航 跳转到搜索
张良留言 | 贡献
Sync NetHub docs from local Markdown
张良留言 | 贡献
Unify tone and terminology across NetHub docs (2026-04-24)
 
(未显示同一用户的3个中间版本)
第1行: 第1行:
= NetHub =
= NetHub =


NetHub bridges device-side Wi-Fi capabilities to the 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>, and the recommended bring-up path is currently <code>SDIO</code>.
The current solution targets Wi-Fi SoCs such as <code>BL616 / BL618 / BL616CL / BL618DG</code>.


== Documentation Guide ==
== Current Status ==


* [[NetHubQuickBringup|NetHubQuickBringup.md]]
{| class="wikitable"
** For customers doing first-time bring-up
|-
** Covers key device/host choices, build steps, module loading, AP connection, and common issues
! Item !! Current status
* [[NetHubArchitecture|NetHubArchitecture.md]]
|-
** For developers who need to understand module boundaries and APIs
| Default interface || <code>SDIO</code>
** Covers device/host layering, public interfaces, and key data flows
|-
* [[NetHubVirtualChannel|NetHubVirtualChannel.md]]
| USB data-path || device-side <code>USB ECM</code> backend implemented
** For customers or application developers who need to transfer private data
|-
** Covers USER channel prerequisites, APIs, and typical usage
| USB control transport || device-side <code>USB ACM</code> transport plumbing implemented
|-
| SPI || not implemented
|-
| USER virtual channel || default interface is <code>SDIO</code>
|-
| Low power || currently <code>BL618DG</code> only
|-
| Optional ATModule control solution || available, but not mandatory
|}


== Current Conclusions ==
== Document Guide ==


* The current primary path is <code>SDIO</code>
Use these documents according to what you need:
* The device-side Wi-Fi backend supports <code>fhost / wl80211</code>
 
* The host control backend is selected at runtime: <code>tty</code> or <code>vchan</code>
{| class="wikitable"
* The control channel and <code>USER virtual channel</code> both run on the same host link
|-
! Document !! Focus
|-
| [[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 interface differences
|-
| [[NetHubVirtualChannel|NetHubVirtualChannel.md]] || USER virtual channel scope, prerequisites, APIs, and limits
|}
 
== Key Points ==
 
* <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>SPI</code> is still a stub and is not ready for bring-up.
* <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 not mandatory.


== In-Repo Reference Directories ==
== In-Repo Reference Directories ==
第32行: 第57行:
== Local Documentation Source ==
== Local Documentation Source ==


* Markdown documents:
The in-repo documentation source is:
** <code>examples/wifi/nethub/docs/</code>


If you need to publish to the online wiki, use these four Markdown documents as the source.
* <code>examples/wifi/nethub/docs/</code>


== Online Wiki ==
== Online Wiki ==


* [https://docs.bouffalolab.com/index.php?title=NetHub]
* [https://docs.bouffalolab.com/index.php?title=NetHub NetHub]
* [https://docs.bouffalolab.com/index.php?title=NetHubQuickBringup]
* [https://docs.bouffalolab.com/index.php?title=NetHubQuickBringup NetHubQuickBringup]
* [https://docs.bouffalolab.com/index.php?title=NetHubArchitecture]
* [https://docs.bouffalolab.com/index.php?title=NetHubArchitecture NetHubArchitecture]
* [https://docs.bouffalolab.com/index.php?title=NetHubVirtualChannel]
* [https://docs.bouffalolab.com/index.php?title=NetHubVirtualChannel NetHubVirtualChannel]

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

  • SDIO is the current default interface for the in-tree bring-up path.
  • USB device-side backend is implemented with ECM + ACM.
  • SPI is still a stub and is not ready for bring-up.
  • nethub core exposes data-path, control path, and virtual channel facades without directly depending on ATModule.
  • The optional ATModule + bflbwifid + bflbwifictrl flow is available, but not mandatory.

In-Repo Reference Directories

  • examples/wifi/nethub
  • components/net/nethub
  • bsp/common/msg_router/linux_host/userspace/nethub

Local Documentation Source

The in-repo documentation source is:

  • examples/wifi/nethub/docs/

Online Wiki