Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ping-Ke Shih <pkshih@realtek.com>
To: Bitterblue Smith <rtl8821cerfe2@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: RE: [PATCH rtw-next 0/5] wifi: rtw88: pci: Support an older design, like RTL8821AE/RTL8812AE
Date: Thu, 29 Oct 2026 01:29:25 +0000	[thread overview]
Message-ID: <13e17aa587024dd3b6d89741e24be5de@realtek.com> (raw)
In-Reply-To: <f5ec572f354f4c67a2a65b2b1676eae0@realtek.com>

Ping-Ke Shih <pkshih@realtek.com> wrote:
> Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> > On 27/10/2026 03:52, Ping-Ke Shih wrote:
> > > Bitterblue Smith <rtl8821cerfe2@gmail.com> wrote:
> > >> This series extends rtw88_pci to support an older design, like
> > >> RTL8821AE, RTL8812AE, RTL8723BE, etc.
> > >
> > > The older design is own-bit ring, and the new is read/write index ring
> > > with buffer descriptor. Can we use 'own-bit' instead of 'old' as the file
> > > name ?
> > >
> >
> > Sure, the file name is not a problem. What about the code? All the functions
> > in pci_old.c are prefixed with "rtw_pci_old", and there is rtw_pci_gen_old
> > and rtw_pci_gen_new. Should I rename all of these?
> 
> I'd prefer having consistent suffix as file name, but I have no good idea
> for the suffix. Maybe, '_ob' means 'own-bit ring'?

Or just '_v0', or '_gen0'?

Think a bit more. Maybe, 'old' is still meaningful for generation of PCI
architecture, since Realtek WiFi PCIE chip has only two kinds of architecture.
If there is third one in the future, that must not be added to rtw88.

At first glance of 'old' days ago, I just want to avoid the implicit naming.



      reply	other threads:[~2026-10-29  1:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23 22:57 [PATCH rtw-next 0/5] wifi: rtw88: pci: Support an older design, like RTL8821AE/RTL8812AE Bitterblue Smith
2026-10-23 22:59 ` [PATCH rtw-next 1/5] wifi: rtw88: Pass RX buffer to rtw_rx_query_rx_desc() Bitterblue Smith
2026-10-23 23:00 ` [PATCH rtw-next 2/5] wifi: rtw88: Pass TX descriptor to rtw_tx_fill_tx_desc() Bitterblue Smith
2026-10-23 23:01 ` [PATCH rtw-next 3/5] wifi: rtw88: pci: Introduce struct rtw_pci_gen Bitterblue Smith
2026-10-24  8:41   ` Luka Gejak
2026-10-28 21:26     ` Bitterblue Smith
2026-10-23 23:02 ` [PATCH rtw-next 4/5] wifi: rtw88: pci: Add functions to support older chips Bitterblue Smith
2026-10-24  8:36   ` Luka Gejak
2026-10-28 17:40     ` Bitterblue Smith
2026-10-23 23:05 ` [PATCH rtw-next 5/5] wifi: rtw88: pci: Handle more RX interrupts for RTL8821AE Bitterblue Smith
2026-10-27  1:52 ` [PATCH rtw-next 0/5] wifi: rtw88: pci: Support an older design, like RTL8821AE/RTL8812AE Ping-Ke Shih
2026-10-27  7:25   ` Luka Gejak
2026-10-27  8:07     ` Ping-Ke Shih
2026-10-28 17:41   ` Bitterblue Smith
2026-10-29  0:51     ` Ping-Ke Shih
2026-10-29  1:29       ` Ping-Ke Shih [this message]

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=13e17aa587024dd3b6d89741e24be5de@realtek.com \
    --to=pkshih@realtek.com \
    --cc=linux-wireless@vger.kernel.org \
    --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