From: Ping-Ke Shih <pkshih@realtek.com>
To: Ezra Buehler <ezra@easyb.ch>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: Jes Sorensen <Jes.Sorensen@gmail.com>,
Kalle Valo <kvalo@kernel.org>,
Martin Kaistra <martin.kaistra@linutronix.de>,
Bitterblue Smith <rtl8821cerfe2@gmail.com>,
Johannes Berg <johannes.berg@intel.com>,
"Reto Schneider" <reto.schneider@husqvarnagroup.com>,
Ezra Buehler <ezra.buehler@husqvarnagroup.com>
Subject: RE: [PATCH v2] wifi: rtl8xxxu: Enable AP mode for RTL8192CU (RTL8188CUS)
Date: Thu, 23 Jan 2025 00:31:46 +0000 [thread overview]
Message-ID: <1da09fe30c7f474eb15c57169e70a87a@realtek.com> (raw)
In-Reply-To: <20250122071512.10165-1-ezra@easyb.ch>
Ezra Buehler <ezra@easyb.ch> wrote:
> From: Ezra Buehler <ezra.buehler@husqvarnagroup.com>
>
> This allows the driver to be used in wireless access point mode on the
> AT91SAM9G25-based GARDENA smart Gateway.
>
> Unfortunately, the data throughput in AP mode appears to be lower than
> with the vendor driver (or in STA mode). Especially when sending, the
> data rate is significantly lower. My measurements performed with iperf3
> and an Edimax EW-7811Un (VID: 7392, PID: 7811) showed a maximum TX rate
> of about 4 Mbits/sec compared to the ~24 Mbits/sec measured with the
> rtl8192cu driver.
I assume the TX rate should be similar in AP mode and STA mode for the
same driver, but still little difference from real AP, which has more
antenna and better capability to TX/RX.
Base on my assumption, I think we can try
1. compare TX rate with/without RF calibration, such as IQK, to ensure
the calibrations work well in AP mode.
2. try fixed TX rate by TX description to check if rate selection problem.
Ping-Ke
next prev parent reply other threads:[~2025-01-23 0:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 7:15 [PATCH v2] wifi: rtl8xxxu: Enable AP mode for RTL8192CU (RTL8188CUS) Ezra Buehler
2025-01-23 0:31 ` Ping-Ke Shih [this message]
2025-02-03 2:40 ` Ping-Ke Shih
2025-02-03 7:55 ` Martin Kaistra
2025-02-03 8:51 ` Ping-Ke Shih
2025-02-04 19:59 ` Ezra Buehler
2025-02-04 20:58 ` Bitterblue Smith
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1da09fe30c7f474eb15c57169e70a87a@realtek.com \
--to=pkshih@realtek.com \
--cc=Jes.Sorensen@gmail.com \
--cc=ezra.buehler@husqvarnagroup.com \
--cc=ezra@easyb.ch \
--cc=johannes.berg@intel.com \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.kaistra@linutronix.de \
--cc=reto.schneider@husqvarnagroup.com \
--cc=rtl8821cerfe2@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox