All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mehmet Fide <mehmet.fide@gmail.com>
To: Luka Gejak <luka.gejak@linux.dev>
Cc: Ping-Ke Shih <pkshih@realtek.com>,
	Bitterblue Smith <rtl8821cerfe2@gmail.com>,
	linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
	mehmet.fide@screeningeagle.com
Subject: Re: [PATCH rtw-next v2 1/2] wifi: rtw88: download the beacon the reserved page was built with
Date: Thu,  1 Oct 2026 13:54:28 +0200	[thread overview]
Message-ID: <20261001115428.2979730-1-mehmet.fide@gmail.com> (raw)
In-Reply-To: <20261001071656.16499-1-luka.gejak@linux.dev>

Hi Luka,

On 2026-10-01 Luka Gejak wrote:
> beacon is written in that branch only, and the caller declares it without an
> initialiser while the free at the end frees whatever it holds. The first page
> always takes that branch today, but the caller cannot see that, so a later
> change in the build would free a stack value. Would you mind initialising it to
> NULL?

Yes, v3 initialises it in rtw_fw_download_rsvd_page(). That is the only
caller of rtw_build_rsvd_page(), so nothing else holds the out-pointer.

> The cover says this path is compile tested only. The feature comes from the
> firmware header rather than from the chip:
[...]
> so another firmware for the same hardware can reach it, and this is the path
> that v1 got wrong. Can it be run once on a device whose firmware has scan
> offload?

Agreed, it should run once. The feature word at offset 0x0c of the
firmware my dongles load is 0x7 for rtw8821c_fw.bin 24.11.0 and 0x0 for
rtw8822b_fw.bin 27.2.0, so neither has bit 8, while rtw8822c_fw.bin
9.9.15 carries 0x1e7. An RTL8822CU dongle is on its way here; v3 goes
out after the scan ran on it with the AP up, once without a countdown
(the download must keep the beacon) and once during one (the scan must
be refused).

Best regards,
Mehmet

  reply	other threads:[~2026-10-01 11:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30  7:44 [PATCH rtw-next v2 0/2] wifi: rtw88: channel switch in AP mode Mehmet Fide
2026-09-30  7:44 ` [PATCH rtw-next v2 1/2] wifi: rtw88: download the beacon the reserved page was built with Mehmet Fide
2026-10-01  7:16   ` [PATCH " Luka Gejak
2026-10-01 11:54     ` Mehmet Fide [this message]
2026-10-05  2:49   ` [PATCH rtw-next " Ping-Ke Shih
2026-09-30  7:44 ` [PATCH rtw-next v2 2/2] wifi: rtw88: support channel switch in AP mode Mehmet Fide
2026-10-01  7:18   ` [PATCH " Luka Gejak
2026-10-01 11:54     ` [PATCH rtw-next " Mehmet Fide
2026-10-05  3:11   ` Ping-Ke Shih
2026-10-05  9:51     ` Mehmet Fide

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=20261001115428.2979730-1-mehmet.fide@gmail.com \
    --to=mehmet.fide@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luka.gejak@linux.dev \
    --cc=mehmet.fide@screeningeagle.com \
    --cc=pkshih@realtek.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.