Clarification on MM8108 monitor mode, frame visibility, and MAC control capabilities

Software Linux
1

Hi,

We are currently setting up the MM8108 platform (EKH01) to form a network and would like to better understand the capabilities and limitations of monitor mode and MAC behaviour, for Linux-based deployments.

We would appreciate clarification on the following areas:

  1. RX path / visibility
  • In monitor mode (e.g., via morse0), are frames delivered:
    a) before or after MAC processing within the firmware?
    b) including control frames such as ACK / RTS / CTS, and frames with failed FCS?
  • Is radiotap-style metadata available (e.g., RSSI, rate, timestamps)?
  • Is there any API or mode that exposes lower-level receive timing information for data frames (beyond beacon-related timing)?
  1. TX path / frame handling
  • Is raw 802.11 frame injection supported from Linux (e.g., sending custom 802.11 headers or management frames)?
  • Is there any mechanism to control transmission timing beyond “send when ready” (e.g., relative timing control, scheduling hints, or alignment to internal clocks)?
  • Are there supported methods to influence or tune MAC behaviour, such as:
    • adjusting contention behaviour
    • modifying backoff characteristics
    • relaxing carrier-sense constraints
  1. MAC control / tuning
  • Which MAC parameters are publicly supported for tuning (e.g., AIFS, CWmin/CWmax, TXOP, CCA threshold)?
  • Are there any recommended configurations for applications that require tighter control over transmission behaviour?
  • Are there debug or engineering builds that expose:
    • more detailed RX metadata
    • additional timing information
    • extended MAC control interfaces
  1. Mesh / 802.11s
  • Is 802.11s mesh mode supported only via Linux (mac80211 / wpa_supplicant)?
  • Is there any support or roadmap for mesh-related functionality in MCU / standalone mode?

Our goal is to understand the extent of visibility and control available at the MAC/PHY boundary for the Linux based development, particularly for applications that are sensitive to timing and transmission behaviour.

Any guidance on supported capabilities, limitations, and recommended approaches would be greatly appreciated.

Thank you.