NetHub：修订间差异

来自Bouffalo Lab Docs
跳转到导航 跳转到搜索
←上一编辑下一编辑→
可视化wikitext
张良​（留言 | 贡献）
133次编辑
小 Sync NetHub docs from local Markdown
张良​（留言 | 贡献）
133次编辑
小 Sync NetHub docs from local Markdown (2026-04-24)
第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-link backend.


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>.
 
== Current Status ==
 
{| class="wikitable"
|-
! Item !! Current status
|-
| Reference bring-up path || <code>SDIO</code>
|-
| USB data path || device-side <code>USB ECM</code> backend implemented
|-
| USB control transport || device-side <code>USB ACM</code> transport plumbing implemented
|-
| SPI || not implemented
|-
| USER virtual channel || currently end-to-end in-tree on <code>SDIO</code>
|-
| Low power || currently <code>BL618DG</code> only
|-
| ATModule dependency || optional example composition only; not a NetHub core dependency
|}


== Documentation Guide ==
== Documentation Guide ==


* [[NetHubQuickBringup|NetHubQuickBringup.md]]
* [[NetHubQuickBringup|NetHubQuickBringup.md]]
** For customers doing first-time bring-up
** first-time bring-up and current support limits
** Covers key device/host choices, build steps, module loading, AP connection, and common issues
* [[NetHubArchitecture|NetHubArchitecture.md]]
* [[NetHubArchitecture|NetHubArchitecture.md]]
** For developers who need to understand module boundaries and APIs
** current device and host architecture, profile boundaries, and APIs
** Covers device/host layering, public interfaces, and key data flows
* [[NetHubVirtualChannel|NetHubVirtualChannel.md]]
* [[NetHubVirtualChannel|NetHubVirtualChannel.md]]
** For customers or application developers who need to transfer private data
** current USER virtual-channel usage and limits
** Covers USER channel prerequisites, APIs, and typical usage


== Current Conclusions ==
== Current Conclusions ==


* The current primary path is <code>SDIO</code>
* <code>SDIO</code> is the current in-tree reference path.
* The device-side Wi-Fi backend supports <code>fhost / wl80211</code>
* <code>USB</code> device-side backend exists now and provides <code>ECM + ACM</code>.
* The host control backend is selected at runtime: <code>tty</code> or <code>vchan</code>
* <code>SPI</code> is still a stub.
* The control channel and <code>USER virtual channel</code> both run on the same host link
* <code>nethub</code> core exposes data-plane, control-path, and virtual-channel facades without directly depending on <code>ATModule</code>.
* The optional <code>ATModule + bflbwifid + bflbwifictrl</code> flow is an example composition, not a hard requirement for NetHub data-path use cases.


== In-Repo Reference Directories ==
== In-Repo Reference Directories ==
第32行： 第51行：
== 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 ==

2026年4月24日 (五) 13:48的版本

NetHub

NetHub bridges device-side Wi-Fi capability to a selected host-link backend.

The current solution targets Wi-Fi SoCs such as BL616 / BL618 / BL616CL / BL618DG.

Current Status

Item Current status
Reference bring-up path 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 currently end-to-end in-tree on SDIO
Low power currently BL618DG only
ATModule dependency optional example composition only; not a NetHub core dependency

Documentation Guide

Current Conclusions

  • SDIO is the current in-tree reference path.
  • USB device-side backend exists now and provides ECM + ACM.
  • SPI is still a stub.
  • nethub core exposes data-plane, control-path, and virtual-channel facades without directly depending on ATModule.
  • The optional ATModule + bflbwifid + bflbwifictrl flow is an example composition, not a hard requirement for NetHub data-path use cases.

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

检索自“https://docs.bouffalolab.com/index.php?title=NetHub&oldid=279”