NetHub - 版本历史

张良：Unify tone and terminology across NetHub docs (2026-04-24)

2026-04-24T14:27:32Z

Unify tone and terminology across NetHub docs (2026-04-24)

张良：Sync NetHub docs from local Markdown (2026-04-24 wording update)

2026-04-24T14:20:25Z

Sync NetHub docs from local Markdown (2026-04-24 wording update)

←上一版本		2026年4月24日 (五) 14:20的版本
第11行：		第11行：
	! Item !! Current status		! Item !! Current status
	\|-		\|-
	\| ~~Reference bring-up path~~ \|\| <code>SDIO</code>		\| Default interface \|\| <code>SDIO</code>
	\|-		\|-
	\| USB data path \|\| device-side <code>USB ECM</code> backend implemented		\| USB data-path \|\| device-side <code>USB ECM</code> backend implemented
	\|-		\|-
	\| USB control transport \|\| device-side <code>USB ACM</code> transport plumbing implemented		\| USB control transport \|\| device-side <code>USB ACM</code> transport plumbing implemented
第19行：		第19行：
	\| SPI \|\| not implemented		\| SPI \|\| not implemented
	\|-		\|-
	\| USER virtual channel \|\| ~~currently end-to-end in-tree on~~ <code>SDIO</code>		\| USER virtual channel \|\| default interface is <code>SDIO</code>
	\|-		\|-
	\| Low power \|\| currently <code>BL618DG</code> only		\| Low power \|\| currently <code>BL618DG</code> only
	\|-		\|-
	\| ATModule ~~dependency~~ \|\| ~~optional example composition only;~~ not ~~a NetHub core dependency~~		\| Optional ATModule control solution \|\| available, but not mandatory
	\|}		\|}

	== ~~Documentation~~ Guide ==		== Document Guide ==

	* [[NetHubQuickBringup\|NetHubQuickBringup.md]]		Use these documents according to what you need:
	** first-time bring-up and current support limits
	* [[NetHubArchitecture\|NetHubArchitecture.md]]
	** current device and host architecture, profile boundaries, and APIs
	* [[NetHubVirtualChannel\|NetHubVirtualChannel.md]]
	** current USER virtual-channel usage and limits

	== ~~Current Conclusions~~ ==		{\| 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 host-link differences
			\|-
			\| [[NetHubVirtualChannel\|NetHubVirtualChannel.md]] \|\| USER virtual channel scope, prerequisites, APIs, and limits
			\|}

			== Key Points ==

	* <code>SDIO</code> is the current in-tree reference path.		* <code>SDIO</code> is the current default interface and the current in-tree reference path.
	* <code>USB</code> device-side backend ~~exists now and provides~~ <code>ECM + ACM</code>.		* <code>USB</code> device-side backend is implemented with <code>ECM + ACM</code>.
	* <code>SPI</code> is still a stub.		* <code>SPI</code> is still a stub and is not ready for bring-up.
	* <code>nethub</code> core exposes data-~~plane~~, control-path, and virtual-channel facades without directly depending on <code>ATModule</code>.		* <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 ~~an example composition~~, not ~~a hard requirement for NetHub data-path use cases~~.		* The optional <code>ATModule + bflbwifid + bflbwifictrl</code> flow is available, but it is not required.

	== In-Repo Reference Directories ==		== In-Repo Reference Directories ==

张良：Sync NetHub docs from local Markdown (2026-04-24)

2026-04-24T13:48:34Z

Sync NetHub docs from local Markdown (2026-04-24)

←上一版本		2026年4月24日 (五) 13:48的版本
第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 ==

张良：Sync NetHub docs from local Markdown

2026-03-17T05:54:34Z

Sync NetHub docs from local Markdown

←上一版本		2026年3月17日 (二) 05:54的版本
第39行：		第39行：
	== 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]

张良：Sync NetHub docs from local Markdown

2026-03-17T05:33:43Z

Sync NetHub docs from local Markdown

←上一版本		2026年3月17日 (二) 05:33的版本
第1行：		第1行：
	= NetHub =		= NetHub =

	NetHub ~~用于把~~ device 侧的 Wi-Fi ~~能力桥接到 host。~~		NetHub bridges device-side Wi-Fi capabilities to the host.

	~~当前方案面向~~ <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>, and the recommended bring-up path is currently <code>SDIO</code>.

	== ~~页面导航~~ ==		== Documentation Guide ==

	* [[NetHubQuickBringup\|~~NetHub 快速上手~~]]		* [[NetHubQuickBringup\|NetHubQuickBringup.md]]
	** ~~面向首次 bringup 的客户~~		** For customers doing first-time bring-up
	** 说明 device/host ~~的关键选择、编译、加载、连接~~ AP ~~和常见问题~~		** Covers key device/host choices, build steps, module loading, AP connection, and common issues
	* [[NetHubArchitecture\|~~NetHub 架构说明~~]]		* [[NetHubArchitecture\|NetHubArchitecture.md]]
	** ~~面向需要理解模块边界和 API 的开发者~~		** For developers who need to understand module boundaries and APIs
	** 说明 device/host ~~分层、公共接口和关键数据流~~		** Covers device/host layering, public interfaces, and key data flows
	* [[NetHubVirtualChannel\|~~NetHub USER Virtual Channel~~]]		* [[NetHubVirtualChannel\|NetHubVirtualChannel.md]]
	** ~~面向需要传输私有数据的客户或应用开发者~~		** For customers or application developers who need to transfer private data
	** 说明 USER ~~通道的前提、API 和典型使用方式~~		** Covers USER channel prerequisites, APIs, and typical usage

	== ~~当前结论~~ ==		== Current Conclusions ==

	* ~~当前主路径是~~ <code>SDIO</code>		* The current primary path is <code>SDIO</code>
	* device 侧 Wi-Fi backend 支持 <code>fhost / wl80211</code>		* The device-side Wi-Fi backend supports <code>fhost / wl80211</code>
	* host 控制 backend ~~运行时二选一：~~<code>tty</code> 或 <code>vchan</code>		* The host control backend is selected at runtime: <code>tty</code> or <code>vchan</code>
	* ~~控制通道和~~ <code>USER virtual channel</code> ~~都承载在同一条~~ host link 上		* The control channel and <code>USER virtual channel</code> both run on the same host link

	== ~~仓内参考目录~~ ==		== 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 ==

			* Markdown documents:
			** <code>examples/wifi/nethub/docs/</code>

			If you need to publish to the online wiki, use these four Markdown documents as the source.

			== Online Wiki ==

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

张良：创建页面，内容为“= NetHub = NetHub 用于把 device 侧的 Wi-Fi 能力桥接到 host。当前方案面向 `BL616 / BL618 / BL616CL / BL618DG` 这类 Wi-Fi SoC，当前推荐 bringup 路径为 `SDIO`。 == 页面导航 == * NetHub 快速上手面向首次 bringup 的客户说明 device/host 的关键选择、编译、加载、连接 AP 和常见问题 * NetHub 架构说明 ** 面向需要理解模…”

2026-03-13T09:19:18Z

创建页面，内容为“= 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 架构说明 ** 面向需要理解模…”

新页面

= NetHub =

NetHub 用于把 device 侧的 Wi-Fi 能力桥接到 host。

当前方案面向 <code>BL616 / BL618 / BL616CL / BL618DG</code> 这类 Wi-Fi SoC，当前推荐 bringup 路径为 <code>SDIO</code>。

== 页面导航 ==

* [[NetHubQuickBringup|NetHub 快速上手]]
** 面向首次 bringup 的客户
** 说明 device/host 的关键选择、编译、加载、连接 AP 和常见问题
* [[NetHubArchitecture|NetHub 架构说明]]
** 面向需要理解模块边界和 API 的开发者
** 说明 device/host 分层、公共接口和关键数据流
* [[NetHubVirtualChannel|NetHub USER Virtual Channel]]
** 面向需要传输私有数据的客户或应用开发者
** 说明 USER 通道的前提、API 和典型使用方式

== 当前结论 ==

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

== 仓内参考目录 ==

* <code>examples/wifi/nethub</code>
* <code>components/net/nethub</code>
* <code>bsp/common/msg_router/linux_host/userspace/nethub</code>

←上一版本		2026年4月24日 (五) 14:27的版本
第1行：		第1行：
	= NetHub =		= NetHub =

	NetHub bridges device-side Wi-Fi capability to a selected host~~-link backend~~.		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 ~~host-link~~ differences		\| [[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 ~~and~~ the ~~current~~ in-tree ~~reference~~ path.		* <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-path, and virtual-channel facades without directly depending on <code>ATModule</code>.		* <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 ~~it is~~ not ~~required~~.		* The optional <code>ATModule + bflbwifid + bflbwifictrl</code> flow is available, but not mandatory.

	== In-Repo Reference Directories ==		== In-Repo Reference Directories ==

NetHub - 版本历史

张良：​Unify tone and terminology across NetHub docs (2026-04-24)

张良：​Sync NetHub docs from local Markdown (2026-04-24 wording update)

张良：​Sync NetHub docs from local Markdown (2026-04-24)

张良：​Sync NetHub docs from local Markdown

张良：​Sync NetHub docs from local Markdown

张良：Unify tone and terminology across NetHub docs (2026-04-24)

张良：Sync NetHub docs from local Markdown (2026-04-24 wording update)

张良：Sync NetHub docs from local Markdown (2026-04-24)

张良：Sync NetHub docs from local Markdown

张良：Sync NetHub docs from local Markdown