From: Larry Finger <Larry.Finger@lwfinger.net>
To: "Jernej Škrabec" <jernej.skrabec@gmail.com>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Driver for rtw8723ds
Date: Thu, 4 May 2023 15:53:59 -0500 [thread overview]
Message-ID: <1901d4d8-bb68-ac5a-0d1f-9bdc46aed43d@lwfinger.net> (raw)
In-Reply-To: <2282070.ElGaqSPkdT@jernej-laptop>
On 5/4/23 15:13, Jernej Škrabec wrote:
> Dne četrtek, 04. maj 2023 ob 21:45:31 CEST je Martin Blumenstingl napisal(a):
>> Hi Larry,
>>
>> On Thu, May 4, 2023 at 9:25 PM Larry Finger <Larry.Finger@lwfinger.net>
>> wrote: [...]
>>
>>>> Can you ask that user to test following commits?
>>>> https://github.com/xdarklight/linux/commit/
>>>> 3866a7a3702f7f24557f2c065b7d4088f7027466
>>>> https://github.com/xdarklight/linux/commit/
>>>> 66fd078556a6bf246337270b2e91d73c079fce2d
>>>>
>>>> Patches are trivial, but some testing needs to be done to confirm the
>>>> driver actually works as intended.
>>>
>>> Jernej,
>>>
>>> The user needs the rtw8723ds driver - the SDIO equivalent of rtw8723du.c
>>> that is used by the USB device. The riscv changes may be needed, but we
>>> are not quite that far yet.
>>
>> Strange, can you please elaborate what you are seeing in terms of riscv?
>> The two commits that Jernej shared are for an update to rtw8723d.c [0]
>> and the addition of a rtw8723ds driver [1]. None of these mentions
>> riscv (at least that's what my tired eyes are seeing today).
>>
>>
>> Best regards,
>> Martin
>>
>>
>> [0]
>> https://github.com/xdarklight/linux/commit/3866a7a3702f7f24557f2c065b7d4088
>> f7027466 [1]
>> https://github.com/xdarklight/linux/commit/66fd078556a6bf246337270b2e91d73c
>> 079fce2d
>
> Problem is that my e-mail client split commit links in two parts. If you
> combine hashes with rest it opens correct commits. Currently, it opens head of
> your master branch, which is by chance risc-v merge commit.
After I compared the links that Martin sent with yours, I figured out the problem.
I downloaded the patches and applied them to my rtw88 repo. The user that wanted
rtw8723ds support has been notified. We will see how it goes.
Thanks,
Larry
next prev parent reply other threads:[~2023-05-04 20:55 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-30 16:51 Driver for rtw8723ds Larry Finger
2023-05-02 19:27 ` Jernej Škrabec
2023-05-04 19:25 ` Larry Finger
2023-05-04 19:45 ` Martin Blumenstingl
2023-05-04 20:13 ` Jernej Škrabec
2023-05-04 20:53 ` Larry Finger [this message]
2023-05-08 18:55 ` Larry Finger
2023-05-08 20:16 ` Martin Blumenstingl
2023-05-09 22:02 ` Larry Finger
2023-05-10 21:07 ` Martin Blumenstingl
2023-05-10 21:47 ` Larry Finger
2023-05-13 10:23 ` Jernej Škrabec
2023-05-13 19:55 ` Larry Finger
2023-05-13 20:13 ` Jernej Škrabec
2023-05-13 21:21 ` Larry Finger
2023-05-15 16:43 ` Jernej Škrabec
2023-05-15 20:23 ` Larry Finger
2023-05-15 20:37 ` Jernej Škrabec
2023-05-15 21:11 ` Martin Blumenstingl
2023-05-16 10:22 ` Martin Blumenstingl
2023-05-16 18:31 ` Larry Finger
2023-05-16 18:48 ` Martin Blumenstingl
2023-05-16 23:41 ` Larry Finger
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=1901d4d8-bb68-ac5a-0d1f-9bdc46aed43d@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=jernej.skrabec@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.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