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
xroumegue has quit [Ping timeout: 480 seconds]
xroumegue has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
davidinux is now known as Guest1867
davidinux has joined #aarch64-laptops
davidinux is now known as Guest1869
Guest1867 has quit [Ping timeout: 480 seconds]
tobhe_ has joined #aarch64-laptops
tobhe has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
tobhe has joined #aarch64-laptops
tobhe_ has quit [Ping timeout: 480 seconds]
hexdump0815 has joined #aarch64-laptops
hexdump01 has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
alfredo has quit [Remote host closed the connection]
chrisl has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
ravikant_ has joined #aarch64-laptops
SpieringsAE has joined #aarch64-laptops
<SpieringsAE> jhovold: I made that adjustment you requested, but I feel like the power-source value should also have a more descriptive define attached to it no?
<SpieringsAE> there don't seem to be any of those for the 8380 pmic though
<jhovold> SpieringsAE: yeah, but that's complicated...
<jhovold> turns out the value of the power source differ from pmic to pmic and supposedly even from pin to pin on the same pmic
<jhovold> no has figured how best to handle this so we stick to raw values there for now
<jhovold> if you have access to the docs, or a dt for some device using the same pin, where the voltage that the power source corresponds to, you can add that as a comment after the property
<SpieringsAE> ah okay thats unfortunate
<jhovold> it's already specified in the crd dtsi in my wip branch so you can assume that's correct:
<jhovold> power-source = <1>; /* 1.8V */
<SpieringsAE> Jeah I will add that comment too
<jhovold> (but add a space before the SI-unit :) )
<SpieringsAE> so 1.8 V
<jhovold> right, thanls
<jhovold> thanks*
<SpieringsAE> np thanks for reviewing, should have seen the reference to that header file in the docs
<SpieringsAE> if i remove serial0 = &uart21, should I turn the other one into serial0 = &uart14? or should I leave it as serial1?
<SpieringsAE> I should also do some continuity check to see if the debug uart is indeed present in that unused connector, time to open her up again lol
<JensGlathe[m]> uart14 is usually used for BT on the x1e boxes
<SpieringsAE> yep thats what its about
<JensGlathe[m]> hmm I wouldn't change the numbering. serial1 = uart14
chrisl has joined #aarch64-laptops
<jhovold> SpieringsAE: yeah, keep the numbering so that if/when the console is enabled it will be at ttyMSM0 as expected
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<SpieringsAE> is there like a dummy usb phy driver? the usb3 redrivers for the usb_mp dont have any configuration option, just vreg and enable
<SpieringsAE> I couldn't really find one scanning through the Documentations
<SpieringsAE> or can I just not put the phy = <>; parameter in there and it will work?
SpieringsAE has quit [Remote host closed the connection]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
SpieringsAE has joined #aarch64-laptops
<exeat> Anyone successfully updated to bios 1.63 on the x13s? Mine hard-reboots just before the final "press enter to reboot" prompt, but the same (usual) procedure did work for 1.60->1.61.
SpieringsAE has quit [Remote host closed the connection]
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #aarch64-laptops
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #aarch64-laptops
<JensGlathe[m]> yes, but with Windows.
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #aarch64-laptops
<noisycoil[m]> Hi all. For anyone who's interested, official Tor Browser nightlies for aarch64 linux are now available at https://nightlies.tbb.torproject.org/nightly-builds/tor-browser-builds/tbb-nightly.2024.12.03/
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #aarch64-laptops
SpieringsAE has joined #aarch64-laptops
<SpieringsAE> it seems my asus does indeed have 2 nxp,ptn3222s, they must be on the underside of the pcb then
<JensGlathe[m]> So the normal config would work, like T14s or HP X14?
<SpieringsAE> I do think so, setting it up rn
<JensGlathe[m]> That's a lot of definitions in thr dt, but worth it
<SpieringsAE> its not too bad tbh
<SpieringsAE> okay here we go br
<SpieringsAE> b
SpieringsAE has quit [Remote host closed the connection]
SpieringsAE has joined #aarch64-laptops
<SpieringsAE> nope still getting: platform a400000.usb: deferred probe pending: dwc3: failed to initialize core
<SpieringsAE> not seeing any other errors though
<exeat> JensGlathe[m]: thanks, I guess Lenovo only tested with Windows this time around :)
<SpieringsAE> nxp,ptn3222 devices have runtimes_status unsupported
<SpieringsAE> There must be some kind of config thing I am overlooking
_whitelogger has joined #aarch64-laptops
<SpieringsAE> here it is
<SpieringsAE> it is exactly the same as the t14s definition from johans fork
<SpieringsAE> that is also the kernel I'm running the for now latest wip/6.12 kernel
<JensGlathe[m]> I'll take a look
<SpieringsAE> I also tried enabling usb_2 earlier, it did not like that lol, but I think the sd card reader is on that one
<SpieringsAE> also my kernel args: root=UUID=d607cc01-0548-4098-8029-747c0ee51452 rw module_blacklist=qcom_edac efi=novamap pd_ignore_unused clk_ignore_unused fw_devlink=off cma=128M rootwait rootflags=noatime,discard loglevel=7
<SpieringsAE> I remember there being an issue before with some stuff in there
<JensGlathe[m]> firing up meld
<SpieringsAE> you found something?
<JensGlathe[m]> can I open a direct chat?
<JensGlathe[m]> element or classic irc
jglathe_sdbox2 has joined #aarch64-laptops
<SpieringsAE> im on irc but yeah sure
<SpieringsAE> no idea how that works though
SpieringsAE has quit [Remote host closed the connection]
SpieringsAE has joined #aarch64-laptops
SpieringsAE has quit [Remote host closed the connection]
SpieringsAE has joined #aarch64-laptops
Caterpillar has quit [Quit: Konversation terminated!]
SpieringsAE has quit [Remote host closed the connection]
whiskey9 has joined #aarch64-laptops
whiskey9 has quit []
SpieringsAE has joined #aarch64-laptops
<SpieringsAE> got usb-a working with the help of JensGlathe: now I'm on to the usb_2 part, I am quite sure that the sd-card reader uses this one
<SpieringsAE> but after enabling it I get a bunch of coredumps and this: gcc_usb20_prim_gdsc status stuck at 'off'
<SpieringsAE> over and over again
<SpieringsAE> is there any device that is already using usb_2 in some way? I can't seem to find an example
minecrell has quit [Quit: Ping timeout (120 seconds)]
minecrell has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
hexa- has quit [Quit: WeeChat 4.4.3]
hexa- has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
<Jasper[m]> Not sure how much different it'll be, but x13s has 2 buses one of which is used for fprint
<Jasper[m]> At best you'll be able to steal the setup for the DTS if the driver is the same, at worst you'll know what to grep for in people's DT files or what laptops to look for if they also have fprint on a separate usb bus
<SpieringsAE> I'm afraid it is too different
<SpieringsAE> the only thing I've seen so far with finger print readers is them using one of the usb-mp ports
<SpieringsAE> there also seems to be an output pin associated with it, tlmm gpio7, so I also somehow need to attach that to it
kalebris has quit [Quit: WeeChat 4.4.3]
<SpieringsAE> I think the t14s has this setup for its fingerprint sensor but I don't think anyone got that one working yet
ravikant_ has quit []
<SpieringsAE> abelvesa: I just saw you mention 3 nxp ptn3222s in your t14s dts, is the third one for the fingerprint scanner?
<SpieringsAE> ^saw it on the mailing list
chrisl has joined #aarch64-laptops
<SpieringsAE> yep I have a third one aswell
<SpieringsAE> on 0x43
<SpieringsAE> how would I name this one, I dont really know what the eusb3 and eusb6 mean
Guest1869 has quit [Ping timeout: 480 seconds]
chrisl has quit [Ping timeout: 480 seconds]
SpieringsAE has quit [Remote host closed the connection]
SpieringsAE has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
<JensGlathe[m]> eusb5 ?
<SpieringsAE> is there any logic behind that? in the dsdt it is USB4
chrisl has quit [Ping timeout: 480 seconds]
<SpieringsAE> unfortunately I fear the issue with that `gcc_usb20_prim_gdsc status stuck at 'off'` is more deeply rooted and a bigger roadblock to getting this working
<JensGlathe[m]> No, I just dimly remember abelvesa using this identifier.
<JensGlathe[m]> the gdsc stuff is a bit... odd. I checked, USB0, 1 , 2 have the same flags set.
<SpieringsAE> some funky firmware stuff maybe?
<SpieringsAE> restricted access or something
<robclark> drive-by note, you can boot el2 to (mostly) rule out fw lolz.. might even get a better external sync/async SError msg (if you have somehow hooked up debug uart)
carter has joined #aarch64-laptops
carter is now known as carterprince
<SpieringsAE> I could theoretically route the uart wires through the grill in the back somehow lol
jglathe_sdbox2 has quit []
<JensGlathe[m]> since the vivobook has the sd card reader it should be enabled (?) when booting up with uefi, so power should be there
phire has quit [Read error: Connection reset by peer]
phire has joined #aarch64-laptops
chrisl has joined #aarch64-laptops
<SpieringsAE> I dont know if there is another enable pin, havent found anything besides the ptn3222 reset
<SpieringsAE> I think it may just be tied high like the 2 tusb522ps
<SpieringsAE> The usb bus just cannot initialize
chrisl has quit [Ping timeout: 480 seconds]
<robclark> anyone got a 7x tcblaunch.exe (or is tcblaunch.exe signed the same way on all the x1 devices.. in which case the question is "anyone got an x1 tcblaunch.exe")
<SpieringsAE> I should have one in case number 2, I still have an intact windows drive, or do you need windows 11 pro for it?
<robclark> I think whatever came installed on the device originally should work, modulo signing (travmurav[m] ?)
sri has joined #aarch64-laptops
<robclark> I'm pretty sure I copied it at some point to try slbounce early on.. but I've failing at finding that thumb-drive atm ;-)
ungeskriptet_ has joined #aarch64-laptops
carterprince has quit [Quit: carterprince]
ungeskriptet has quit [Ping timeout: 480 seconds]
ungeskriptet_ is now known as ungeskriptet
<macc24> is there something to probe i2c buses on windows?
chrisl has joined #aarch64-laptops
<\[m]> ok, alternate.nl got the t14s back in stock this week in some days - better be worth to be in red for haha
<Jasper[m]> It never is bro, don't do that shit
<JensGlathe[m]> I abstained
<JensGlathe[m]> There's enough to play with
SpieringsAE has quit [Remote host closed the connection]
<\[m]> it's the company it's fine
chrisl has quit [Ping timeout: 480 seconds]
<JensGlathe[m]> huh
<JensGlathe[m]> even then
<JensGlathe[m]> My day job isn't tinkering with arm64 laptops
<kuruczgy[m]> robclark: sha256 should be 5dfcd0253b6ee99499ab33cac221e8a9cea47f3fdf6d4e11de9a9f3c4770d03d
<kuruczgy[m]> (I am actually surprised Matrix just let me upload an exe file...)
<kuruczgy[m]> Let me know if it works for you, I really hope it's not per-device signed or something...
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
jhovold has quit [Ping timeout: 480 seconds]
<robclark> kuruczgy[m]: thx
sri has quit [Ping timeout: 480 seconds]
chrisl has joined #aarch64-laptops
chrisl has quit [Ping timeout: 480 seconds]
svarbanov has quit [Ping timeout: 480 seconds]
svarbanov has joined #aarch64-laptops
<\[m]> ok I cancelled the t14s for now will buy it next month - anyway not the period I want to be putting strain on logistical networks