From: lonthn <lonthn@163.com>
To: linux-wireless@vger.kernel.org
Subject: Re: [rtw89] PCI Passthrough Issue: rtl8852be on ARM VM (Ubuntu host/OpenWrt guest)
Date: Thu, 12 Jun 2025 20:38:52 +0800 (CST) [thread overview]
Message-ID: <757a4801.a04e.197642679a4.Coremail.lonthn@163.com> (raw)
In-Reply-To: <684A83E1.25166C.00001@m16.mail.163.com>
At 2025-06-12 15:38:09, lonthn@163.com wrote:
>Thanks for your quick response.
>
>> This looks like interoperability problem of 36-bit DMA.
>> If you have below commit in your guest OS:
>> 1fd4b3fe52ef ("wifi: rtw89: pci: support 36-bit PCI DMA address")
>>
>> Please also have below commit to rollback 32-bit DMA.
>> aa70ff0945fe ("wifi: rtw89: pci: early chips only enable 36-bit DMA on specific PCI hosts")
>>
>> With the latest kernel, you can just comment code as below to use 32-bit DMA.
>
>I tried it and found that it still doesn't work
>
>> I have not ever tried passthrough, so I'm not sure if it can work.
>> Can I know how different the passthrough is?
>
>You can refer to this: https://docs.kernel.org/driver-api/vfio.html
>
>> Does rtl8852be work on host OS?
>
>I'm trying, but when I load the 8852be driver, strangely, I get nothing.
>$> dmesg |grep 8852be
>no message!
>$> lsmod |grep rtw
>rtw_8852be 16384 0
>rtw_8852b 352256 1 rtw_8852be
>rtw89pci 61440 1 rtw_8852be
>rtw89core 569344 2 rtw89pci,rtw_8852b
>It looks like my device is not detected
I've confirmed that the host system is working
next prev parent reply other threads:[~2025-06-12 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 7:38 [rtw89] PCI Passthrough Issue: rtl8852be on ARM VM (Ubuntu host/OpenWrt guest) lonthn
2025-06-12 12:38 ` lonthn [this message]
2025-06-13 0:55 ` Ping-Ke Shih
-- strict thread matches above, loose matches on Subject: below --
2025-06-11 14:35 lonthn
2025-06-12 1:33 ` Ping-Ke Shih
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=757a4801.a04e.197642679a4.Coremail.lonthn@163.com \
--to=lonthn@163.com \
--cc=linux-wireless@vger.kernel.org \
/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.