NetHub:修订间差异

来自Bouffalo Lab Docs
跳转到导航 跳转到搜索
张良留言 | 贡献
创建页面,内容为“= NetHub = NetHub 用于把 device 侧的 Wi-Fi 能力桥接到 host。 当前方案面向 <code>BL616 / BL618 / BL616CL / BL618DG</code> 这类 Wi-Fi SoC,当前推荐 bringup 路径为 <code>SDIO</code>。 == 页面导航 == * NetHub 快速上手 ** 面向首次 bringup 的客户 ** 说明 device/host 的关键选择、编译、加载、连接 AP 和常见问题 * NetHub 架构说明 ** 面向需要理解模…”
 
张良留言 | 贡献
Unify tone and terminology across NetHub docs (2026-04-24)
 
(未显示同一用户的4个中间版本)
第1行: 第1行:
= NetHub =
= NetHub =


NetHub 用于把 device 侧的 Wi-Fi 能力桥接到 host。
NetHub bridges device-side Wi-Fi capability to a selected host interface.


当前方案面向 <code>BL616 / BL618 / BL616CL / BL618DG</code> 这类 Wi-Fi SoC,当前推荐 bringup 路径为 <code>SDIO</code>。
The current solution targets Wi-Fi SoCs such as <code>BL616 / BL618 / BL616CL / BL618DG</code>.


== 页面导航 ==
== Current Status ==


* [[NetHubQuickBringup|NetHub 快速上手]]
{| class="wikitable"
** 面向首次 bringup 的客户
|-
** 说明 device/host 的关键选择、编译、加载、连接 AP 和常见问题
! Item !! Current status
* [[NetHubArchitecture|NetHub 架构说明]]
|-
** 面向需要理解模块边界和 API 的开发者
| Default interface || <code>SDIO</code>
** 说明 device/host 分层、公共接口和关键数据流
|-
* [[NetHubVirtualChannel|NetHub USER Virtual Channel]]
| USB data-path || device-side <code>USB ECM</code> backend implemented
** 面向需要传输私有数据的客户或应用开发者
|-
** 说明 USER 通道的前提、API 和典型使用方式
| 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
|}


== 当前结论 ==
== Document Guide ==


* 当前主路径是 <code>SDIO</code>
Use these documents according to what you need:
* device 侧 Wi-Fi backend 支持 <code>fhost / wl80211</code>
* host 控制 backend 运行时二选一:<code>tty</code> 或 <code>vchan</code>
* 控制通道和 <code>USER virtual channel</code> 都承载在同一条 host link 上


== 仓内参考目录 ==
{| class="wikitable"
|-
! 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 ==


* <code>examples/wifi/nethub</code>
* <code>examples/wifi/nethub</code>
* <code>components/net/nethub</code>
* <code>components/net/nethub</code>
* <code>bsp/common/msg_router/linux_host/userspace/nethub</code>
* <code>bsp/common/msg_router/linux_host/userspace/nethub</code>
== Local Documentation Source ==
The in-repo documentation source is:
* <code>examples/wifi/nethub/docs/</code>
== Online Wiki ==
* [https://docs.bouffalolab.com/index.php?title=NetHub NetHub]
* [https://docs.bouffalolab.com/index.php?title=NetHubQuickBringup NetHubQuickBringup]
* [https://docs.bouffalolab.com/index.php?title=NetHubArchitecture NetHubArchitecture]
* [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