ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
baspar[m] has joined #aarch64-laptops
amstan has joined #aarch64-laptops
juergh has joined #aarch64-laptops
juergh is now known as Guest394
Prawn[m] has joined #aarch64-laptops
wiizzard has joined #aarch64-laptops
harvests[m] has joined #aarch64-laptops
Nao[m] has joined #aarch64-laptops
jenneron[m] has joined #aarch64-laptops
bluerise_ has joined #aarch64-laptops
bluerise has quit [Ping timeout: 480 seconds]
<quinine> > <> results:... (full message at <>)
<clover[m]> Thanks now I'm more confused
<quinine> according to mozilla, firefox should have about 100 points in Speedometer. 🤔
<clover[m]> Arm64 different?
<quinine> Does it not perform well on x13s? 🤔
<HdkR> According to Mozilla on what hardware?
<quinine> clover[m]: Maybe something to do with gpu?
<HdkR> The CPU obviously isn't as fast as an Intel 13900k :P
<quinine> HdkR: makes sense, proportionally, chrome has the same regression.
<quinine> I don't know why chrome and chromium have different performance in mozilla's test.
<quinine> Maybe chrome has PGO enabled but chromium doesn't? 🤔
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
Lucanis has quit [Remote host closed the connection]
Lucanis has joined #aarch64-laptops
<akaWolf0> clover[m]: yeah, in Windows they do it right :)
iivanov has joined #aarch64-laptops
iivanov has quit [Quit: Leaving.]
iivanov has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
iivanov has quit [Quit: Leaving.]
<danielt> I finally knocked up a patch to get gnome-shell/wayland running on systems with an external monitor. Not yet sure if it is an approach that can work upstream but people are welcome to test it:
laine has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
iivanov has quit [Quit: Leaving.]
laine has joined #aarch64-laptops
<leezu> robclark: Does cros use/expose the Qualcomm DSP Hexagon cores or has plans to do so? Lazor/sc7180 for example has a 5 TOPS compute remote processor device that can be used to offload compute expensive workloads like ML model inference, but only the modem remote processor (mpss) seems supported in upstream Linux yet for sc7180. If anyone is interested, I found this article
<leezu> gives a good overview over the DSPs
laine has quit [Ping timeout: 480 seconds]
<robclark> leezu: I don't believe we use the dsp
laine has joined #aarch64-laptops
<exeat> Seems like a nice little compute unit:
<exeat> (Buried under a mountain of proprietary cruft)
hightower2 has joined #aarch64-laptops
laine has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
<amstan> leezu: every time we considered using the any DSP it's been like hitting a brick wall
<amstan> i believe audio uses some of it, but nothing else
<HdkR> The Hexagon is a pretty cool piece of kit. Shame about that userspace accessibility
Lucanis0 has joined #aarch64-laptops
Lucanis has quit [Ping timeout: 480 seconds]
<amstan> it's the usual story, hardware might nice but software lockdown ruins it
iivanov has quit [Quit: Leaving.]
<HdkR> I can understand that context-switching the usage of it is hard
<HdkR> But GPUs have had this solved for a long time, I'm sure DSPs could sort their shit out at some point
<clover[m]> HkdR: would FEXRootFSFetcher work on arch linux arm?
<steev> danielt: to test that patch, i'm asssuming i should revert ?
laine has joined #aarch64-laptops
<danielt> steev: Testing either way round is somewhat useful since increasing confidence it won't cause regressions is good (if I got the logic in mutter right when gnome-shell/wayland should fire up with or without the hack patch in the kernel).
<HdkR> clover[m]: Yes, it would just fetch an Ubuntu image to use under FEX.
<HdkR> We don't have our tooling setup to generate Arch x86 rootfs images yet
<danielt> steev: ... but take a look at the chat on the issue tracker before deciding whether or not to invest time in testing... other contributors who posted today are right, the patch I proposed is at best a stop-gap since it simply maintains the illusion that you can look up "the" plane for a CRTC (it does not add smarts to mutter to help it adopt the "best" planes)
<steev> danielt: oh i did, i figured i'd test it anyway :) i don't like gimping the driver
<clover[m]> Hope it works
<steev> it's a stopgap either way
laine has quit [Ping timeout: 480 seconds]
agl7-x13s has joined #aarch64-laptops
<agl7-x13s> Good Evening! :-)
<leezu> amstan: I thought the aDSP and cDSP are widely used on Android. What kind of issues did you face?
<amstan> leezu: i'm talking about chromeos
<amstan> i'm sure it's widely used on android, that's what qcom designs their stuff for
<leezu> Yes. I mean why do you face issues when trying to use it with cros?
<amstan> signing, documentation, toolchains, etc
<amstan> for a lot of stuff you have a choice to be an "app" in a proprietary DSP OS ecosystem or not use the DSP at all
<amstan> there's no open source option
<leezu> I see. For cDSP there is a mostly open source toolchain with llvm and, though in the end the code still nedes to be linked with a few proprietary libraries from the hexagon sdk
<amstan> you cannot run baremetal on most of those, at least it was not the case when i was looking into this for the sensor hub
<leezu> Yes, but the same applies to Android? There should be some OS on the DSP and Linux userspace can interact with it over IPC to load/invoke DSP libraries. They may need to be signed for aDSP, but unsigned should work with cDSP
<leezu> According to the article, I was expecting /dev/adsprpc-smd /dev/cdsprpc-smd devices for the aDSP / cDSP driver, but they are missing. aDSP and cDSP are declared in the sc7180 dts though
<leezu> For the modem DSP, also declared in above commit, I can see it get's initialized: "remoteproc remoteproc0: Booting fw image qcom/sc7180-trogdor/modem-nolte/mba.mbn, size 283296"
<leezu> ("qcom-q6v5-mss 4080000.remoteproc: MBA booted without debug policy, loading mpss")
<konradybcio> that article describes a downstream stack using a 4.14 bsp kernel
agl7-x13s has quit [Quit: Leaving]
iivanov has joined #aarch64-laptops
<clover[m]> someone making a chromiumOS spin for the x13s? :P
<clover[m]> steev: i have some time this afternoon to test daniel's mutter patch if you want to update a branch with the kernel patch reverted
<steev> lenovo-x13s-linux-6.3.y-ironrobin
<clover[m]> kewl
<leezu> I think the problem for sc7180 is that qcom,fastrpc isn't declared in the dts for the adsp and cdsp. The FastRPC driver implements the IPC mechanism for the DSPs
<leezu> That's in contrast to the sc8280xp.dtsi, which correctly declares fastrpc. Anyone with a X13s may be able to confirm if they see the /dev/adsprpc-smd /dev/cdsprpc-smd devices, assuming remoteproc kernel configs are enabled (CONFIG_REMOTEPROC=y CONFIG_REMOTEPROC_CDEV=y CONFIG_QCOM_PIL_INFO=y CONFIG_QCOM_RPROC_COMMON=y CONFIG_QCOM_Q6V5_COMMON=y CONFIG_QCOM_Q6V5_ADSP=y
<ajhalaney[m]> personally steev I'd leave the kernel hack instead of hoping people move the patching to mutter... but that's my two cents :)
<steev> squeeky wheel gets the grease, or some such
<steev> i thought you fedora peeps were all "upstream first!" types :P
<clover[m]> mutter 44.1 with danielt's patch works
<HdkR> Aw, there was a recent folio change but it doesn't solve the 5gbit unhandled context fault problem
<HdkR> well, changes the backtrace at least
<HdkR> What a nightmare
<clover[m]> this mutter patch works better than the kernel patch. if i remove cable while in clamshell mode the internal screen actually recovers now
<steev> thanks... i'll keep it around as well... currently there's a broken unit test with some ubuntu patch so waiting on that for 44.1 in debian
<steev> though, a few of the wayland tests are also flakey on arm64
<HdkR> On arm64 or on X13s?
<steev> arm64
<steev> they don't use the actual x13s stuff to run
<HdkR> I'm mostly thinking about the GPU instability
<steev> the event-delivery one is the test that's holdup
<steev> the gpu itself isn't tested, afaik
<steev> but who knows; i'm currently building it on the rock-5b, though it takes 18 minutes there, versus 8 on the x13s
<HdkR> ah cool
<steev> clover[m]: out of curiosity, does it run the tests there or only if you specify for it to?
<clover[m]> I commented out a testing part that blew up on my x13s and M1 pro
<clover[m]> I noticed manjaro arm devs did that so i guess its an arm64 issue
<steev> i've only had it "not fail" once in my builds - wherein it only failed on the same test that fails on amd64
<qzed> I finally got around to try out the proper usb-multi-port patchset
<qzed> worked on the first try, yay
<qzed> so I can finally drop my hacked-together monstrosity
<HdkR> Went through the process of updating my desktop to a newer kernel just to see if this was a new kernel bug with this ethernet adapter. Seems fine there
<HdkR> Got a device with an out of tree driver, so it's always exciting trying to get that working again
<steev> qzed: oh nice... that reminds me... vkoul how is sc8180x looking? :D
<steev> what the f
<steev> and now it succeeded
<qzed> any ideas why I get no display on 6.4-rc2 (sc8180x)?
<qzed> instead I get
<qzed> [drm:dp_aux_isr [msm]] ERROR Unexpected DP AUX IRQ 0x01000000 when not busy