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
<bamse> HdkR: no, that's it
<bamse> HdkR: the problem is that if you don't have venus firmware, then venus probe fails and sync_state never happens...so your interconnects are going at full speed forever
<bamse> HdkR: it's been a while, but johan reported that to reduce his battery life with 2-3 hours
<craftyguy> oh wow
<HdkR> bamse: Oh, perfect for me then. I'll leave the firmwares untouched :D
systwi has joined #aarch64-laptops
<steev> heh
aradhya7 has quit [Quit: Connection closed for inactivity]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
<travmurav[m]> <jglathe> "is it a good idea to set the..." <- ideally firmware sets it for you IMO
<travmurav[m]> ^ (... set t he bt address via dt), bridge cut it a bit short
<travmurav[m]> it's obviously pretty problematic if one hardcodes the address, but if some firmware either knows what it actually is or allocates a stable-random one from the local pool then it would mostly "just work"
jglathe has joined #aarch64-laptops
<travmurav[m]> javierm: Hi! we talked about fedora expecting ebbr-ish dtb being passed from firmware. For x13s we expect the dtb to be in esp, does the installer preserve the file if it wants to wipe the esp?
jglathe has quit [Ping timeout: 480 seconds]
jglathe has joined #aarch64-laptops
<Dantheman825[m]> is there additional firmware I should have for the X13s' webcam?
<Dantheman825[m]> or is it mostly just having the right kernel config for it?
<Dantheman825[m]> right now, the camera subsystem is acknowledged, but it's split into like 30 options
jglathe has quit [Ping timeout: 480 seconds]
hexdump01 has quit []
hexdump0815 has joined #aarch64-laptops
jglathe has joined #aarch64-laptops
Caterpillar has quit [Quit: Konversation terminated!]
f_ has quit [Ping timeout: 480 seconds]
Caterpillar has joined #aarch64-laptops
Guest12299 has joined #aarch64-laptops
<Guest12299> hi
<Guest12299> here is thinkpad chat?
Guest12299 has quit [Remote host closed the connection]
jglathe has quit [Ping timeout: 480 seconds]
f_ has joined #aarch64-laptops
jglathe has joined #aarch64-laptops
jglathe has quit [Remote host closed the connection]
jglathe has joined #aarch64-laptops
jglathe has quit [Remote host closed the connection]
jglathe has joined #aarch64-laptops
<jglathe> @craftyguy: got bootmac working now, udev-triggered doesn't work though. Essential appears to be some delay. Config now is set up default bt mac in the dts, and start bootmac in the root crontab @reboot with 7 seconds delay. It comes up with a unique address then.
jglathe has quit [Remote host closed the connection]
jglathe has joined #aarch64-laptops
<craftyguy> debugging udev rules is always fun :P
<jglathe> didn't really change it, but I had a lot of this delayed stuff with BT. Previous hack was also root crontab, but static address. This is an improvement.
<craftyguy> was udev unable to call the script, or do you know what the problem was?
<jglathe> couldn't find anything, only the flickering logos (bt connection) and stopping it by calling bootmac with my parameters directly. Assumed it was the already-active BT from the default address in the dts, but this was not the case either. crontab without delay also gives the flickering. udev might work with a delay, decided to play it safe and not depend on it. Works now as expected and desired. BT address will be set
<jglathe> regardless if its enabled or not.
<jglathe> :shrug:
<craftyguy> oh maybe it's related to the bt module loading late (so the device hasn't initialized by the time udev triggers? I'm just guessing...)
<craftyguy> on pmOS (for now at least), the driver is builtin so the device is available like right when "switch_root" happens from the initfs, and the udev rule is in the rootfs...
<jglathe> This happened starting with mantic IMO. Anyway, next for now... you happy on pmOS?
<craftyguy> yeah, but I'm a bit biased :P
<jglathe> who isn't
<craftyguy> (I'm on the pmOS core team)
<craftyguy> so pmOS everywhere, on everything, I always say.
<craftyguy> :P
<steev> Dantheman825[m]: userland needs changes to make the cam work
<steev> Dantheman825[m]: you need https://gitlab.freedesktop.org/camera/libcamera-softisp/-/branches one of these softisp branches, and you need to make sure to enable the `simple/simple` ipa/pipeline (it won't by default)
<steev> and my experience was, just installing it to /usr/local wasn't enough, and you have to export the directory for gstreamer things to see it (check the readme)
jglathe has quit [Ping timeout: 480 seconds]
<steev> jenneron[m]: konradybcio posted up a patchset to fixup some things with sc8180x today
<jenneron[m]> nice
<jenneron[m]> unfortunately i'm on 6.1.69 kernel..
<steev> same :D
<jenneron[m]> mainline has broken UFS
<jenneron[m]> also it seems that my patch didn't fix touchpad
<jenneron[m]> so this question is still open
<jenneron[m]> it may still be interrupt though. i'm wondering if we can somehow make interrupt more "responsive"
<konradybcio> primus can be used and put to sleep without clk_ignore_unused pd_ignore_unused with my latest patches..
<jenneron[m]> oh that's nice
<konradybcio> it's not yet "full suspend", but it should be better than today
<jenneron[m]> konradybcio: btw if you're interested i got sound working on it
<jenneron[m]> also, do you have UFS problems on high load?
<konradybcio> i have no hardware in hand, only remote boards
<jenneron[m]> i see
<konradybcio> primus has an nvme
<konradybcio> ufs too, but i didn't stress it much
<jenneron[m]> konradybcio: gnome-disks read benchmark setting 250 samples of 1000 MiB makes it die in a few seconds
<jenneron[m]> maybe dd if=/dev/sda of=/dev/null would do the same?
<konradybcio> i'll check on tuesday
<jenneron[m]> i suppose i can check with dd on my system