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
exeat has quit [Ping timeout: 480 seconds]
kuter has joined #aarch64-laptops
quinine has joined #aarch64-laptops
<quinine>
<clover[m]> "quininer: have you had a..." <- I need to catch a flight today, I will try tomorrow :D
kuter has quit [Ping timeout: 480 seconds]
<clover[m]>
<steev> "but maybe you are, or for some..." <- oh yeah they don't have that set
<abelvesa>
colemickens: which is bleeding edge right now
<abelvesa>
colemickens: a couple of us are still upstreaming support for it (the SoC mainly and then CRD)
<abelvesa>
colemickens: I do not own any of the x1e laptops yet (maybe soon). I do have access to CRD, where I test most of the stuff I upstream.
<abelvesa>
colemickens: if the installer I shared doesn't boot with full display, then we might need to disable the mdss entirely in devicetree in order to allow display to stay on (as a hack until we figure out what is different on your device when compared to CRD)
colemickens has quit [Quit: Connection closed for inactivity]
HgGamer has quit [Remote host closed the connection]
colemickens has joined #aarch64-laptops
kuter has joined #aarch64-laptops
<abelvesa>
hggamer: can you please swap the orientation of the type-c thumbdrive you booted from ?
<abelvesa>
orientation is not yet handled correctly in kernel (yet)
<abelvesa>
that's the reason the /dev/sda2 cannot be found
exeat has joined #aarch64-laptops
<robclark>
oh, already dts on list for one of the new laptops.. that is nice to see
kuter has quit [Quit: Leaving]
<abelvesa>
robclark: yes, but we need to make sure it is correct. I have a feeling that copying stuff from CRD dts into a new one for a different laptop is going to make it harder to figure out what is broken on that specific laptop.
<abelvesa>
robclark: so I guess the question here is: where did the all that information from that DT come from? was it based on some schematics or ... ?
<robclark>
I think the crd dts with a bunch of stuff removed
<abelvesa>
robclark: most likely, yes, by comparisson
<robclark>
probably not completely incorrect, I assume OEMs used the crd as starting point for their design
<abelvesa>
yeah, that's probably true
strongtz[m] has joined #aarch64-laptops
<strongtz[m]>
abelvesa: I sent that dts to the list. I think everything enabled in that dt should be correct :P
<abelvesa>
strongtz[m]: I figured it was you :)
<abelvesa>
strongtz[m]: what did you check against ? acpi tables ?
<strongtz[m]>
yes, acpi tables
<Jasper[m]>
strongtz[m]: I have some questions about that (I can't look at the dts atm)
<Jasper[m]>
Are they using i2c-hid for any of the keyboard/touchpads by any chance?
<Jasper[m]>
If yes, how did you figure out the needed gpio and irq pins for that? Assuming those components work with your tree.
<strongtz[m]>
Jasper: Yes they are all using i2c-hid, except for the surface pro 11
<strongtz[m]>
The interrupt pin could be found from I2cSerialBusV2 of the HID device in DSDT
<strongtz[m]>
uh no, I mean GpioInt below that I2cSerialBusV2
<Jasper[m]>
strongtz[m]: Reason why I'm asking is because I have an older device I was looking to get working, but the pin assignments seem to not line up.
<strongtz[m]>
uh, I guess the gpio pin looks weird right?
<strongtz[m]>
that might be a virtual pdc gpio
<Jasper[m]>
strongtz[m]: `0x01C0` for the keyboard interrupt basically hahahaha
<Jasper[m]>
strongtz[m]: Any idea how to handle those? I've heard something about debugging the windows driver while hammering keys, but that seems very complicated
<strongtz[m]>
what laptop is it exactly?
<Jasper[m]>
strongtz[m]: Galaxy Book2 Go (sc7280), dsdt is in the build repo from aarch64-laptops
<Jasper[m]>
I'm not asking you to do the porting work for me, but I'd appreciate a pointer to getting that part of interpreting the dsdt correct
<Jasper[m]>
Because I've postponed the work for that reason...
<strongtz[m]>
Jasper: try gpio39
<Jasper[m]>
strongtz[m]: How'd you get to that conclusion?
<Jasper[m]>
(I'll try this weekend)
<Jasper[m]>
Jasper[m]: There's also just the regular pins that I'd need to figure out anyways. Hence the question.
possiblemeatball has joined #aarch64-laptops
<Jasper[m]>
* There's also scl and sda that I'd need to figure out anyways. Hence the question.
alfredo has joined #aarch64-laptops
<Jasper[m]>
<strongtz[m]> "Jasper: try gpio39" <- Also upstream dtsi's basically only use this for spi chip select it seems
possiblemeatball has quit [Remote host closed the connection]
<strongtz[m]>
Jasper[m]: but it can be used as a normal gpio isn't it
<Jasper[m]>
You may know that better than I do
possiblemeatball has joined #aarch64-laptops
alfredo1 has joined #aarch64-laptops
<Jasper[m]>
<strongtz[m]> "that might be a virtual pdc gpio" <- or tlmm? aspire1 (different soc, I know) uses an interrupt pin mapped in that
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
<Jasper[m]>
Eh no it seems to be some pdc port indeed
<Jasper[m]>
no idea how to determine which one though, I'd guess the 0x01c0 is the irq to use
<Jasper[m]>
448
<Jasper[m]>
How do you select the pdc port from that? The description in the binding is a tad unclear to me
<colemickens>
oh hey, it's strongtz[m] !
<strongtz[m]>
<Jasper[m]> "How'd you get to that conclusion..." <- I'm still looking at the decompilation of the windows driver and trying to understand it lol
<Dylanger>
Huh, the WiFi + BT on the Acer aarch64 Chromebook/MT8195 is just a PCIe card
<Dylanger>
It's a mt7921, I was expecting it to be on-SoC
<colemickens>
abelvesa: thanks for all that information!
<strongtz[m]>
colemickens: My tree is simply based on his tree :)
alfredo has quit [Ping timeout: 480 seconds]
<jhovold>
steev: yeah, venus support is blocked on the missing fw, but there was also some discussion about reworking the driver (but that should not be a precondition)
<robclark>
abelvesa: btw, should ACPI boot be working (ie. enough to run an installer)? (And if so, do you know the minimum kernel version where it would work)
possiblemeatball has quit [Remote host closed the connection]
HgGamer has quit [Remote host closed the connection]
KieranBingham[m] has joined #aarch64-laptops
<KieranBingham[m]>
I've got a sim card in my x13s now - and I seem to be able to get it connected, but it's always got a really low signal strength. Is there anything to control or adjust signal power that I need to change for that ? or is it just ... really is low signal (even though my phone next to the laptop has full signal?)
<clover[m]>
i noticed mine often has low signal too, but it doesn't really affect the connection, which always seems strong enough for fast web browsing
possiblemeatball has joined #aarch64-laptops
kuter has joined #aarch64-laptops
kuter has quit [Quit: Leaving]
possiblemeatball has quit [Quit: Quit]
kuter has joined #aarch64-laptops
colemickens1 has joined #aarch64-laptops
enyalios_ is now known as enyalios
colemickens is now known as colemickens_irc
colemickens1 is now known as colemickens
Liso[m] has joined #aarch64-laptops
Las[m] has joined #aarch64-laptops
ahoneybun[m] has joined #aarch64-laptops
aigotchi[m] has joined #aarch64-laptops
Nei[m] has joined #aarch64-laptops
ajhalaney[m] has joined #aarch64-laptops
akawolf[m] has joined #aarch64-laptops
arisu has joined #aarch64-laptops
AlexMarty[m] has joined #aarch64-laptops
anarchron has joined #aarch64-laptops
anonymix007[m] has joined #aarch64-laptops
Anton[m]1 has joined #aarch64-laptops
ArtyomK[m] has joined #aarch64-laptops
averyfreeman[m] has joined #aarch64-laptops
baspar[m] has joined #aarch64-laptops
bruno_rodriguezz[m] has joined #aarch64-laptops
bumble[m] has joined #aarch64-laptops
Leandro[m]12 has joined #aarch64-laptops
pz[m]1 has joined #aarch64-laptops
cmeerw[m] has joined #aarch64-laptops
Eighth_Doctor has joined #aarch64-laptops
QiuWenbo[m] has joined #aarch64-laptops
<abelvesa>
robclark: I don't think that works at all
Dantheman825[m] has joined #aarch64-laptops
dcavalca has joined #aarch64-laptops
davidebeatrici[m] has joined #aarch64-laptops
EricCurtin[m] has joined #aarch64-laptops
edrex[m] has joined #aarch64-laptops
emily[m]1 has joined #aarch64-laptops
EnigmaCurry[m] has joined #aarch64-laptops
enserzo[m] has joined #aarch64-laptops
firlaev-hans-fiete[m] has joined #aarch64-laptops
freekurt[m] has joined #aarch64-laptops
Guest10980 has joined #aarch64-laptops
harvests[m] has joined #aarch64-laptops
harvestz[m] has joined #aarch64-laptops
HCG[m] has joined #aarch64-laptops
hlr[m] has joined #aarch64-laptops
szclsya[m] has joined #aarch64-laptops
jenneron[m] has joined #aarch64-laptops
jjardon[m] has joined #aarch64-laptops
juergh1 has joined #aarch64-laptops
kazek[m] has joined #aarch64-laptops
konradybcio has joined #aarch64-laptops
LoganLeland[m] has joined #aarch64-laptops
<robclark>
oh.. that is unfortunate.. it would be a way for .iso installer images to work enough to install updates
LikeNeosMatrix[m] has joined #aarch64-laptops
lun[m] has joined #aarch64-laptops
z3ntu has joined #aarch64-laptops
Lucy[m]1 has joined #aarch64-laptops
malvi[m]1 has joined #aarch64-laptops
matrix638[m] has joined #aarch64-laptops
matthew[m]1234 has joined #aarch64-laptops
mothenjoyer69 has joined #aarch64-laptops
mynery[m] has joined #aarch64-laptops
NomadNaomie[m] has joined #aarch64-laptops
nekogirl[m] has joined #aarch64-laptops
neobrain[m] has joined #aarch64-laptops
nicholascw[m] has joined #aarch64-laptops
Nick[m]1234 has joined #aarch64-laptops
nick1343[m] has joined #aarch64-laptops
\[m] has joined #aarch64-laptops
Nao[m] has joined #aarch64-laptops
nscnt[m] has joined #aarch64-laptops
owc[m] has joined #aarch64-laptops
patzek[m] has joined #aarch64-laptops
possiblemeatball has joined #aarch64-laptops
PterKoczka[m] has joined #aarch64-laptops
pine-clover[m] has joined #aarch64-laptops
DocGalaxyBlock[m] has joined #aarch64-laptops
<JensGlathe[m]>
Booting from USB was the main pain point last year to bring up Volterra, way more forgiving from SSD. Also, getting it to boot reliably (enough) from USB type-c, you need to jump through the modules / adsp hoops first. That kept me quite busy for a while.
<robclark>
abelvesa: btw any new non-obvious kconfig? (Ie. without "X1E" in the config name.).. not able to mount rootfs from usb drive (tried both orientations).. see "dwc3: failed to initialize core" for a000000.usb and a600000.usb
Prawn[m] has joined #aarch64-laptops
psydroid[m] has joined #aarch64-laptops
KhalIshaIii[m] has joined #aarch64-laptops
<robclark>
JensGlathe[m]: there is a chicken vs. egg problem if you can't boot from usb :-P
valida-69[m] has joined #aarch64-laptops
qzed has joined #aarch64-laptops
resuenehparg[m]1 has joined #aarch64-laptops
sally[m]123 has joined #aarch64-laptops
sally[m]1234 has joined #aarch64-laptops
qzed is now known as Guest11090
cenunix[m] has joined #aarch64-laptops
shjim[m] has joined #aarch64-laptops
<JensGlathe[m]>
so what else is new 😆
SintayewGashaw[m] has joined #aarch64-laptops
Sobek[m] has joined #aarch64-laptops
sporos11[m] has joined #aarch64-laptops
steevdave[m] has joined #aarch64-laptops
stefan-schmidt[m] has joined #aarch64-laptops
steveej[m] has joined #aarch64-laptops
Stirl[m] has joined #aarch64-laptops
Sayatomoki[m] has joined #aarch64-laptops
sz3m3k[m] has joined #aarch64-laptops
M0133oracle[m] has joined #aarch64-laptops
underpantsgnome[m] has joined #aarch64-laptops
travmurav[m] has joined #aarch64-laptops
Segfault[m] has joined #aarch64-laptops
vadikas[m] has joined #aarch64-laptops
valentine has joined #aarch64-laptops
Nios34[m] has joined #aarch64-laptops
wiizzard has joined #aarch64-laptops
wiley[m] has joined #aarch64-laptops
dlx[m] has joined #aarch64-laptops
<JensGlathe[m]>
Finally. pop-os kernel for aarch64 has built on X13s running pop, only 63 mins
<lollaritits[m]>
thats just modemmanager being modemmanager
<lollaritits[m]>
those readings are utter crap
<lollaritits[m]>
on any linux laptop i ever had they were always low
<KieranBingham[m]>
aha interesting ...
<abelvesa>
robclark: which tree?
<robclark>
strongtz's tree, which is based on your tree.. starting point is a fedora(ish) config for x13s
<JensGlathe[m]>
aaand its back: skin_temp_thermal-virtual-0 +47.0°C
<JensGlathe[m]>
no real idea what it was, I removed only 2 commits, one was for iio (dunno where that came from)
<abelvesa>
robclark: check if the repeaters have probed
<robclark>
I'm not actually getting a console.. so a bit hard to check much.. I do have qmp phy things as =y
<robclark>
I am building the initrd on x13s so maybe misses some modules?
<abelvesa>
CONFIG_PHY_QCOM_EUSB2_REPEATER
<abelvesa>
in defconfig is module
<abelvesa>
try building it in
<robclark>
ahh, that was missing (=n)
<abelvesa>
that is definitely needed
kuter has quit [Quit: Leaving]
jhovold has quit [Ping timeout: 480 seconds]
<robclark>
ahh, looks like I also need CONFIG_PHY_QCOM_EUSB2
kuter has joined #aarch64-laptops
<Jasper[m]>
Ahhhh, alright
kuter has quit [Remote host closed the connection]