Linux wireless drivers development
 help / color / mirror / Atom feed
From: Stefan Lippers-Hollmann <s.l-h@gmx.de>
To: Ping-Ke Shih <pkshih@realtek.com>
Cc: "rtl8821cerfe2@gmail.com" <rtl8821cerfe2@gmail.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"chewitt@libreelec.tv" <chewitt@libreelec.tv>
Subject: Re: [PATCH 1/3] wifi: rtlwifi: Move code from rtl8192de to rtl8192d-common
Date: Sun, 15 Sep 2024 08:04:34 +0200	[thread overview]
Message-ID: <20240915080434.564d1c66@mir> (raw)
In-Reply-To: <4c4aa8160119935e48f9da679b502f80da4c0fc7.camel@realtek.com>

Hi

On 2024-03-13, Ping-Ke Shih wrote:
> On Wed, 2024-03-13 at 06:49 +0100, Stefan Lippers-Hollmann wrote:
> > On 2024-03-13, Bitterblue Smith wrote:
> > > Create the new module rtl8192d-common and move some code into it from
> > > rtl8192de. Now the rtl8192de driver (PCI) and the new rtl8192du driver
> > > (USB) can share some of the code.
[...]
> > Using the firmware from https://github.com/lwfinger/rtl8192du/,
> > it would be great if someone could publish the necessary firmware
> > to linux-firmware.
> >
> > MD5:
> > abccba1e9bb456eb81dfc88502a56300  /lib/firmware/rtlwifi/rtl8192dufw.bin
> >
> > SHA256:
> > 9b51f15642b7f2d41e8369d7df956f92333c09699d8a88039081a8bdc77242a1  /lib/firmware/rtlwifi/rtl8192dufw.bin
>
> I can do that after this patchset get merged.

As kernel v6.11 premiering with rtl8192du (which works well) isn't that
far away, I'll just drop a reminder about publishing the corresponding
rtlwifi/rtl8192dufw.bin firmware image to linux-firmware.

Regards
	Stefan Lippers-Hollmann

Post scriptum: Apologies if I missed a corresponding patch to
               linux-firmware.git.

  parent reply	other threads:[~2024-09-15  6:04 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12 22:18 [PATCH 1/3] wifi: rtlwifi: Move code from rtl8192de to rtl8192d-common Bitterblue Smith
2024-03-12 22:20 ` [PATCH 2/3] wifi: rtlwifi: Adjust rtl8192d-common for USB Bitterblue Smith
2024-03-13  3:46   ` Ping-Ke Shih
2024-03-13 22:47     ` Bitterblue Smith
2024-03-14  1:20       ` Ping-Ke Shih
2024-03-14 13:49         ` Bitterblue Smith
2024-03-12 22:23 ` [PATCH 3/3] wifi: rtlwifi: Add new rtl8192du driver Bitterblue Smith
2024-03-13  5:49   ` Ping-Ke Shih
2024-03-13 22:45     ` Bitterblue Smith
2024-03-14  0:34       ` Ping-Ke Shih
2024-03-12 23:21 ` [PATCH 1/3] wifi: rtlwifi: Move code from rtl8192de to rtl8192d-common Bitterblue Smith
2024-03-13  3:53   ` Ping-Ke Shih
2024-03-13 22:40     ` Bitterblue Smith
2024-03-13  2:16 ` Ping-Ke Shih
2024-03-13 22:39   ` Bitterblue Smith
2024-03-13  5:49 ` Stefan Lippers-Hollmann
2024-03-13  5:55   ` Ping-Ke Shih
2024-03-13  6:18     ` Stefan Lippers-Hollmann
2024-03-13  6:25       ` Ping-Ke Shih
2024-03-13 22:44         ` Bitterblue Smith
2024-03-13 22:41     ` Bitterblue Smith
2024-03-14  0:28       ` Ping-Ke Shih
2024-09-15  6:04     ` Stefan Lippers-Hollmann [this message]
2024-09-16  7:42       ` Ping-Ke Shih
2024-09-16 10:21         ` Stefan Lippers-Hollmann
2024-03-13  8:58 ` Kalle Valo
2024-03-13 22:46   ` Bitterblue Smith
2024-03-14  8:18     ` Kalle Valo
2024-03-14  8:42       ` Kalle Valo
2024-03-14 13:50         ` 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=20240915080434.564d1c66@mir \
    --to=s.l-h@gmx.de \
    --cc=chewitt@libreelec.tv \
    --cc=linux-wireless@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox