On Thu, 14 Mar 2024 at 14:31, Marc Gonzalez <mgonzalez@xxxxxxxxxx> wrote: > > On 13/03/2024 16:53, Dmitry Baryshkov wrote: > > > On Wed, 13 Mar 2024 at 17:09, Marc Gonzalez wrote: > > > >> On 05/03/2024 20:20, Kalle Valo wrote: > >> > >>> Marc Gonzalez wrote: > >>> > >>>> I need to build a kernel + rootfs + FW to test the proposed solution, > >>>> then I can spin a formal submission. > >>> > >>> Yeah, please do test this to make sure we are not missing anything :) > >> > >> I used buildroot ( https://buildroot.org ) to generate a kernel + rootfs > >> for my board (a variation of qcom/msm8998-mtp.dts) > >> > >> Not sure if I must use the vendor FW blobs? Or if I can use the blobs > >> from linux-firmware-20240115.tar.xz (as supported by BR2). > >> > >> > >> All I see from the ath10k driver (with debugging cranked to the max) is: > >> > >> [ 0.539801] ath10k_snoc 18800000.wifi: Adding to iommu group 0 > >> [ 0.541941] ath10k_snoc 18800000.wifi: snoc xo-cal-data return -22 > >> [ 0.543633] ath10k_snoc 18800000.wifi: supply vdd-3.3-ch1 not found, using dummy regulator > >> [ 0.544002] ath10k_snoc 18800000.wifi: qmi msa.paddr: 0x0000000094400000 , msa.vaddr: 0x(____ptrval____) > >> [ 0.544271] ath10k_snoc 18800000.wifi: snoc probe > >> > >> > >> # ip link > >> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue qlen 1000 > >> link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 > >> 2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000 > >> link/ether 34:27:92:82:48:ec brd ff:ff:ff:ff:ff:ff > >> > >> No wlan device at this point. > > > > Do you have pd-mapper, rmtfs and tqftpserv running? You also need to > > have wlanmdsp.mbn in the same directory as modem.mbn for your platform > > (see how this is handled for sdm845). > > If these points are implemented and you still don't have the wlan, > > please check for tqftpserv messages in syslog. > > I first tried using buildroot, which doesn't package these tools AFAICT. > I have now generated a debian rootfs, which does package them. > > > >> I got shell-shock from reading these setup steps: > >> > >> https://wiki.postmarketos.org/wiki/Qualcomm_Snapdragon_835_(MSM8998)#WLAN > >> https://github.com/jhugo/linux/blob/5.5rc2_wifi/README > > > > These readmes are mostly correct. You don't need qrtr now, it is > > provided by the kernel. pd-mapper (protection-domain-mapper), > > tqftpserv and rmtfs usually can be installed from your distro. > > Can you explain a little bit why all the steps are required > just to be able to talk to the ath10k IP block? > > It's just an MMIO device, right? > > wifi: wifi@18800000 { > compatible = "qcom,wcn3990-wifi"; > reg = <0x18800000 0x800000>; > reg-names = "membase"; > > Is the IP block behind some kind of switch that must be programmed > by a remote processor on the SoC? It has a separate core, with the firmware to load, etc. For some reason the firmware is loaded in a complex way, via the modem remoteproc. -- With best wishes Dmitry
