Re: [RFC PATCH v3 0/4] wifi: rtl8xxxu: implement AP mode for 8188EU

[Georg Müller]

Just to give a litte update:

Am 14.03.26 um 00:14 schrieb Bitterblue Smith:
> What are the issues? Were they happening with your original patch
> which only added supports_ap and max_macid_num?
>
> Another thing still missing is the macid in the TX descriptor
> (rtl8xxxu_fill_txdesc_v3).

I added setting the macid in rtl8xxxu_fill_txdesc_v3 and the other comments to the
patches.

There are still some issues:

In a test setup, I connected 5 different devices to a host running with a 8188eu wifi dongle
running in AP mode and a web server running on it.

All were able to fetch a web page served by the host.

Sometimes the connection was a bit stuck, but this recovered after some time.

In the logs of the server with the 8188eu dongle, I sometimes observed the following messages
in dmesg (with debug messages turned on):

  C2H TX report type 2
  rtl8188e_handle_ra_tx_report2: len: 24 items: 3
  rtl8188e_handle_ra_tx_report2: TX report item 0 not valid
  rtl8188e_handle_ra_tx_report2:  valid: 0 retry: 0 0 0 0 0 drop: 0
  rtl8188e_handle_ra_tx_report2:  valid: 0 retry: 0 0 0 0 0 drop: 0
  rtl8188e_handle_ra_tx_report2:  valid: 1 retry: 5 0 0 0 0 drop: 0

another thing which sometimes occurred:

  rtl8xxxu_read8(020a)   = 0x00, len 1   # <- repeated 50-70 times
  rtl8xxxu_send_beacon_frame: Failed to read beacon valid bit


What I observed on one of the clients was DUP ping responses. I will try to debug this with
a wifi capture device.

Best regards,
Georg