robclark changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Chrome OS Trogdor Devices - Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630 - Lenovo ThinkPad X13s - and various other snapdragon laptops) - https://oftc.irclog.whitequark.org/aarch64-laptops
<steev>
good to hear!
echanude has joined #aarch64-laptops
leezu has quit [Ping timeout: 480 seconds]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
mcbridematt has quit [Ping timeout: 480 seconds]
mcbridematt has joined #aarch64-laptops
jglathe_ has quit [Remote host closed the connection]
jglathe_ has joined #aarch64-laptops
Mathew has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
svarbanov has joined #aarch64-laptops
svarbanov__ has quit [Read error: Connection reset by peer]
<jglathe_x13s>
jenneron[m] thanks I thought as much, and I thought the adsp firmware is in the initramfs (it is) and will be used (it isn't).
<jglathe_x13s>
and I'm at a loss why. It is in the main/ part of initramfs
<jglathe_x13s>
I guess there's a clue, will check. I did some substitutions in the hooks file for the desired source paths, maybe therein lies the issue
<jglathe_x13s>
thanks for confirming
<jenneron[m]>
jglathe_x13s: you also need remoteproc initramfs modules included in initramfs, otherwise these modules will get probed in rootfs and firmware will be loaded in rootfs as well
<jenneron[m]>
and you need not only adsp firmware, but other remoteproc'es too, because if you load module on initramfs stage it will expect all firmware files there
<abby>
i've still not had any luck getting my x13s keyboard to work with the defconfig merged into void's dotconfig, even when all the options are identical (except for a couple that seem wholly irrelevant, like preempt)
<abby>
if i had to guess this means that something in void's dotconfig is set when it shouldn't be, are there any known module incompatibilities, things that should be blacklisted or turned off?
<alx__>
could someone kindly pastebin me the supposed content of Windows/System32/drivers/DriverData/QUALCOMM/fastRPC/ ?
Caterpillar has joined #aarch64-laptops
Caterpillar has quit []
<alx__>
I am trying to get the remoteproc to work with fastrpc on my x13s since a few days and somehow seems off, even via unsigned access I get a 0x8000600 error which is a rpc failure. But the code work, it seems to be somehting about the host machine. Anyone tried that before?
<alx__>
also the device tree lacks adsp and slpi, they are available on windows