NetHub：修订间差异

来自Bouffalo Lab Docs
跳转到导航 跳转到搜索
←上一编辑
可视化wikitext
张良​（留言 | 贡献）
133次编辑
小 Sync NetHub docs from local Markdown (2026-04-24)
张良​（留言 | 贡献）
133次编辑
小 Unify tone and terminology across NetHub docs (2026-04-24)
 
（未显示同一用户的1个中间版本）
第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>.
第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 interface 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 for the in-tree bring-up 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 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

  • 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

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