ChanServ 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> lenovo downloads i think
<craftyguy> erebion[m]: ya my range was that terrible, until I loaded the other BT firmware thing
<steev> you can extract it with innoxtract or whatever it is
<craftyguy> it downloads the bt fw from lenovo and extracts it, but url/filename are there along with the innoxtract command
<steev> also... JensGlathe[m] ? i think? ^
<steev> and we have audio \o/
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
Caterpillar has quit [Read error: Connection reset by peer]
Caterpillar has joined #aarch64-laptops
Lucanis has quit [Ping timeout: 480 seconds]
Lucanis has joined #aarch64-laptops
tobhe_ has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
hipboi has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
hexdump0815 has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
<steev> gwolf: you *might* have to modprobe.blacklist=ipa with the debian kernel though, i really have no idea why but it seems to cause a panic early at boot
hipboi has quit [Quit: hipboi]
paddymahoney has quit [Ping timeout: 480 seconds]
paddymahoney has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
\\ has quit [Ping timeout: 480 seconds]
flto has joined #aarch64-laptops
\\ has joined #aarch64-laptops
hipboi has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
jhovold has joined #aarch64-laptops
hipboi has quit [Quit: hipboi]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
alfredo has quit [Quit: alfredo]
paddymahoney has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
paddymahoney has joined #aarch64-laptops
hipboi has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
paddymahoney has quit [Ping timeout: 480 seconds]
sally is now known as Guest5932
sally has joined #aarch64-laptops
Guest5932 has quit [Ping timeout: 480 seconds]
paddymahoney has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
paddymahoney has quit [Ping timeout: 480 seconds]
srinik has joined #aarch64-laptops
paddymahoney has joined #aarch64-laptops
paddymahoney has quit [Ping timeout: 480 seconds]
paddymahoney has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
flokli has quit [Quit: WeeChat 4.4.2]
flokli has joined #aarch64-laptops
Caterpillar has quit [Quit: Konversation terminated!]
chrisl has joined #aarch64-laptops
paddymahoney has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
hipboi has quit [Quit: hipboi]
paddymahoney has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
hogliux has joined #aarch64-laptops
hipboi has joined #aarch64-laptops
<hogliux> Does anybody have a working realtime clock on their x1e80100 on linux (specifically yoga slim 7x)? It's annoying me that I always need to wait for internet for my clock to be correct.
chrisl has joined #aarch64-laptops
<kuruczgy[m]> Nope, no RTC for me either. It's quite annoying with captive portals on public Wi-Fi, because HTTPS won't work without a correct clock, but you need to get through the captive portal to get internet...
<kuruczgy[m]> Also Yoga Slim 7x question: any update on the speakers?
<kuruczgy[m]> srinik: Do you by chance know where the .tplg file for the Yoga Slim 7x can be sourced from?
<travmurav[m]> lol the pmic rtc is extra locked out on x1e apparently? https://elixir.bootlin.com/linux/v6.12-rc2/source/arch/arm64/boot/dts/qcom/x1e80100-pmics.dtsi#L226
<erebion[m]> <kuruczgy[m]> "Nope, no RTC for me either. It's..." <- Yeah, but you usually know at least what day it is and can set an approximate time and then connect.
<travmurav[m]> I didn't undertand why they locked out setting time but killing the whole thing?
<erebion[m]> Just use Iodine, all troubles gone, lol
chrisl has quit [Ping timeout: 480 seconds]
<hogliux> Hmm this is the ACPI table for the RTC on the yoga slim 7x: https://pasteboard.co/tvqaXXNM8mL8.png The _GRT method gets the current time. Doesn't look all to complicated. Does it maybe only work in EL2?
<hogliux> s/to/too/
<travmurav[m]> it only works with PEP
<travmurav[m]> because "i2c" there is not i2c but a virtual mailbox into the pep driver code
<hogliux> :-( PEPs!
<hogliux> kuruczgy[m]: I have the tplg file for the Yoga Slim 7x on my repo: https://github.com/hogliux/yoga7x-firmware/commit/72b9dafe12b8543c4177e903784ac951bfff5a95 But you also need an alsa UCM file which I haven't been able to work on yet.
<kuruczgy[m]> hogliux: Where did you get it from? You created it?
<hogliux> No macc24 took the CRD tplg file's source and removed any references to hardware that does not exist in the yoga slim 7x and re-compiled it. See discussion starting here: https://oftc.irclog.whitequark.org/aarch64-laptops/2024-09-27#33604042;
<hogliux> If you take the CRD's tplg, you'll get a ton of dsp errors. With macc24's version, alsamixer now detects everything correctly but you still get an error in dmesg that the UCM profile is missing. I'm swamped with work currently so won't be able to work on the UCM file anytime soon. But there are UCM files for the CRD so it shouldn't be that hard to adopt to the slim 7x.
<hogliux> Oh sorry it was JosDehaes and not macc24: https://oftc.irclog.whitequark.org/aarch64-laptops/2024-09-27#33605896
<kuruczgy[m]> Thanks!
<krzk> hogliux: kuruczgy[m]: instead of alsa UCM you could also try setting mixers manually - just to debug. Maybe my testing script will be useful: https://github.com/krzk/tools/blob/master/tests-var/qcom/test-spkr-qcom-sc8380xp-crd.sh
<hogliux> krzk: OMG it works!
<hogliux> krzk: Just s/Twitter/Tweeter/ in the script and it works. krzk: you are amazing!
<krzk> Ah yes, there was a typo. Happy tha tit helps
<hogliux> kuruczgy[m]: FYI: use my tplg file and the run krzk's script after s/Twitter/Tweeter/ and also edit line 296
paddymahoney has quit [Ping timeout: 480 seconds]
<hogliux> Only the left speaker but, hey, progress!
<krzk> hogliux: can you send pull request with your topology? It's codeLinaro, not github/gitlab, but also patches would work: https://git.codelinaro.org/linaro/qcomlt/audioreach-topology
<krzk> hogliux: or if it is too complicated maybe you have audioreach topology repo forked somewhere with your commit, so I would cherry-pick and send as pull req
paddymahoney has joined #aarch64-laptops
<hogliux> krzk: I don't have login for codeLinaro so how can I open a PR there?
<krzk> yeah, that's the question... You can always send it via email (git request-pull), but then patch will be fine as well.
<krzk> I am working on moving this outside of CodeLinaro
<hogliux> Oh beat you to it: https://pastebin.com/rn4wv1t1 . However, please, wait until JosDehaes gives his approval here. Because he created the tplg file and did all the work. It should really be him who submits the patch not me.
chrisl has joined #aarch64-laptops
<gwolf> steev: sweet! That is with 6.12, I guess
<hogliux> JosDehaes: is it ok for me to PR your tplg file for the Lenovo Slim 7x? Or do you want to submit the PR?
alfredo has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
<leland[m]> I left my x13s on overnight and theres still good battery life
<kuruczgy[m]> hogliux: krzk: Cool, thanks, will try it out when I have some time.
<kuruczgy[m]> Another question: Is it possible to damage the speakers with a bad software configuration? AFAIK the asahi people have a whole speaker monitoring system for the Macbooks just to keep the speakers safe.
chrisl has joined #aarch64-laptops
<jhovold> kuruczgy[m]: yes, it is
<jhovold> we limited the volume in the kernel driver for the x13s for now for that reason
<jhovold> afaik, there's no limit yet for x1e
<hogliux> kuruczgy[m]: Yes definitely. There is no speaker protection. I did a -12dB on my audio wav file in audacity before playing to be on the safe side. But be really sure that you call `aplay` with the correct format settings so that you don't start playing noise.
<kuruczgy[m]> jhovold: Could you give some pointers perhaps for what we should pay attention to to minimize the chances of damage? E.g. should we replicate the x13s kernel volume limit?
<krzk> hogliux: please rebase because you pushed some mixup from CodeLinaro, which I dropped while moving to Github, but what's more important - I need there source code, not BIN file
<krzk> hogliux: something like commit 56b403ffe857dcfb264783a4a50728272fffd887 in that repo
paddymahoney has quit [Ping timeout: 480 seconds]
weirdtreething has quit [Read error: Connection reset by peer]
weirdtreething has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<hogliux> krzk: That's because JosDehaes decompiled the binary tplg file with `alsatplg -d`, removed the hardware relating to the audio jack and then re-compiled it with `alsatplg`
<krzk> hogliux: not good, we need the sources
<hogliux> krzk: sorry I can't help with that
<krzk> sure, I get it
<hogliux> krzk: Maybe ask JosDehaes. But I think he just decompiled the tplg file of the CRD.
hipboi has quit [Quit: hipboi]
<macc24> ooo sound
<freekurt[m]> What's the second most supported aarch64 laptop behind the x13s that has at least 8GB of RAM? I don't see support matrix wikis anywhere.
<Jasper[m]> freekurt[m]: Aspire 1 if you can find the sku with 8GB RAM
<Jasper[m]> Also a significant amount of chromebooks
<travmurav[m]> is it really second if it has 150hrs of suspend compared to x13s's 30?
<travmurav[m]> sad bridge didn't pass  over
<travmurav[m]> \<del\>
<freekurt[m]> So Aspire 1 has better suspend?
<travmurav[m]> s/better/working I'd say but maybe you don't want a rather slow 7c
<macc24> 7c chromebooks have great support too
<travmurav[m]> aspire1 has feature parity with windows with an exception of an internal mic
<travmurav[m]> but 7c is not the fastest soc, it's good enough for like browser and office tasks but maybe not expect much more
<freekurt[m]> Is it only 4gb ram tho?
<travmurav[m]> most skus are, presumably there are some with 8, never seen anyone claim they have it
<travmurav[m]> but seen listed online at some point iirc
paddymahoney has joined #aarch64-laptops
<JosDehaes[m]> <hogliux> "krzk: Maybe ask JosDehaes. But I..." <- No I didn't 😁. I based off the source of the CRD
<hogliux> JosDehaes[m]: That's why I ask :-D
<JosDehaes[m]> Here is my source: https://github.com/joske/audioreach-topology
<hogliux> JosDehaes[m]: I'll close my PR then. You can open a new PR with krzk here: https://github.com/linux-msm/audioreach-topology
<JosDehaes[m]> Ok, I'm at a conference right now, can do later
<jhovold> kuruczgy[m]: short answer is we do not know what the safe limits are
<jhovold> there was a bug in the original audio support which capped the volume, and when I fixed that I didn't want to be responsible for people blowing their speakers so added the limit in the machine driver
<jhovold> as that's the level most people had been using without damaging anything
<jhovold> it may be possible to go higher, but we need to find someone willing to risk their speakers in order to determine that
<jhovold> was hoping we'd be able to have support for the dsp speaker protection in a not too distant future
<jhovold> but yeah, try to keep the volume down when enabling audio and try not send any square waves to speakers
<jhovold> to the speakers*
hogliux has quit [Remote host closed the connection]
alfredo has joined #aarch64-laptops
<JosDehaes[m]> hogliux: I don't have my yoga with me (I'm abroad), but at least you can remove all the headset stuff from that script
<JosDehaes[m]> I'll have a look when I'm back (Saturday) to see if this helps to make UCM files
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
alfredo has quit [Read error: Connection reset by peer]
paddymahoney has quit [Remote host closed the connection]
chrisl has joined #aarch64-laptops
paddymahoney has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
DJVG has quit [Quit: Page closed]
<macc24> iirc there's been a ucm file somewhere for the CRD
<macc24> and it was quite simple
hogliux has joined #aarch64-laptops
<jhovold> macc24: the crd ucm files are already upstream:
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<\[m]> 3th place laptop? I guess mmm the x1e yoga?
spoonerandrew has quit [Quit: Connection closed for inactivity]
<JosDehaes[m]> yes, I tried based on the UCM files of the CRD, but was not successful so far
srinik has quit [Ping timeout: 480 seconds]
<JosDehaes[m]> that's why I didn't create a PR earlier, but now hogliux confirmed it's actually working
hogliux has quit [Quit: Page closed]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
cyrinux has quit []
<HdkR> Who will get to sparse first, Adreno or Asahi? :D
cyrinux has joined #aarch64-laptops
<krzk> macc24: hogliux: jhovold: just a note that latest ALSA UCM for X1E80100 CRD is for kernels with DisplayPort, which is not in mainline/next, so use a bit older commit (pre DP). Also the DP one has some issues on my Debian - I think I wrote conflicting devices in wrong or incomplete way.
<krzk> so this needs some improvements for final DP support. It's on my todo list, but if anyone likes UCM files more, go ahead :)
<macc24> by the time i get around to it it'll probably be in linux-next already
<\[m]> what is sparse?
kettenis_ has quit [Ping timeout: 480 seconds]
are-you-dead-yet has joined #aarch64-laptops
are-you-dead-yet has left #aarch64-laptops [#aarch64-laptops]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
kettenis has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
jhovold has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
sri has quit [Ping timeout: 480 seconds]
ellyq has quit []
ellyq has joined #aarch64-laptops
<steev> gwolf: it's in -next, so you can request it to be added in the debian kernel (but stable is cc'd so it should make it back at some point)