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
echanude has quit [Ping timeout: 480 seconds]
nothorseface has joined #aarch64-laptops
davidinux is now known as Guest3025
davidinux has joined #aarch64-laptops
Guest3025 has quit [Ping timeout: 480 seconds]
nothorseface has quit []
tobhe has joined #aarch64-laptops
tobhe_ has quit [Ping timeout: 480 seconds]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
<JensGlathe[m]>
I‘ve put the ACPI dump and HWInfo log on aarch64-laptops/build, lumag already merged it. Good to know re ASUS BIOS update. And from peeking into hp and acer BIOS files I had the impression they support both variants.
<travmurav[m]>
I wonder if anyone with uart (or at least earlycon=efifb) tried to boot purwa
<JensGlathe[m]>
Not yet.
alfredo has quit [Quit: alfredo]
<JensGlathe[m]>
Just done so, it goes over earlycon (looking very normal), starts booting up further and resets. Video time I guess. But breakfast first.
<travmurav[m]>
interesting, perhaps different gpu then?
<travmurav[m]>
as we discussed with robclark recently
<travmurav[m]>
or ah you mean "time to make a video to look at the logs closer" not "seems like logs get to the video init", though still I think we kinda guessed that cpu/gpu clusters are the only different thing it seems
<travmurav[m]>
inb4 just wrong gpu firmware/microcode
<JensGlathe[m]>
Probably. I just took the Snapdragon Dev Kit stick and booted with it. Ofc it has its firmwares in the initramfs.
<JensGlathe[m]>
The GPU names itself X1-45, the SoC SnapDragon 8cx nextgen. But for a first try it at least comes over earlycon, so any missing cores don‘t seem to stop it.
<travmurav[m]>
for cpu the firmware should just reject psci_on(8..11)
<travmurav[m]>
so it's fine, but I think gpu wise the os touches registers which can easily break things if the registers are different
<travmurav[m]>
and/or if the microcode/firmware is different I guess
<JensGlathe[m]>
Will do another try without specific firmwares. Later.
<travmurav[m]>
well I think after the first error like ^^, can assume the system is dead
<JensGlathe[m]>
as in never?
<travmurav[m]>
never?
<JensGlathe[m]>
never ever going to work
<travmurav[m]>
I mean I believe if you catch an oops in linux, it's safe to assume the internal state is broken so all later errors could be attributed to the first
<JensGlathe[m]>
that would be my assumption.
<travmurav[m]>
well I guess time to disable bwmon and try again? :D
<JensGlathe[m]>
bwmon?
<travmurav[m]>
[icc_bwmon], the thing that oopsed on the photo
<travmurav[m]>
a module even, should be easy :D
<JensGlathe[m]>
oh okay. Yeah but now its family day, no time for a rabbit hole like this now
<travmurav[m]>
yeah :D
<travmurav[m]>
iirc bwmon is for optimizing the performance levels of interconnects (speeding them up/slowing down on demand)
<travmurav[m]>
ohhhhhh
<travmurav[m]>
ohhhhhhhhhh
<travmurav[m]>
there is three bwmons for each cluster
<travmurav[m]>
since one of those certainly doesn't exist in hw
<travmurav[m]>
yeah
<travmurav[m]>
and thus you get sync abort due to touching non-existent registers
<travmurav[m]>
that makes sense to me
<travmurav[m]>
well maybe there is more stuff to be killed like this later but probably need to handle those one-at-a-time
<JensGlathe[m]>
nice, will look into this... later. Thank you for the pointer!
<JensGlathe[m]>
Looks like we need a purwa dtsi, though
<travmurav[m]>
tbh, I'd argue it might be better designed as overlays even, so we can build x1e and x1p dtb from the same sources easily, like it's done for db410c and rb5 right now for example, but have whole x1p-40.dtbo
<travmurav[m]>
so like we'd just have a makefile change to add x1p variant of the device
<travmurav[m]>
and smart tools like dtbloader could then detect and do whatever (apply overlay/ pick by suffix/ fixup via code...)
<travmurav[m]>
but well, need to make it work first :D
<JensGlathe[m]>
Can we delete nodes in a dtbo? Or set it disabled?
<travmurav[m]>
Only set disabled
<travmurav[m]>
Should be enough for most cases tho
<travmurav[m]>
We fixed GPU zap shader node for that for example
<JensGlathe[m]>
Good point
anozetsubou has quit [Ping timeout: 480 seconds]
anozetsubou has joined #aarch64-laptops
crisma has quit [Read error: Connection reset by peer]
srinik has joined #aarch64-laptops
srinik has quit [Ping timeout: 480 seconds]
nothorseface has joined #aarch64-laptops
nothorseface has quit [Ping timeout: 480 seconds]
nothorseface has joined #aarch64-laptops
srinik has joined #aarch64-laptops
jhovold has joined #aarch64-laptops
eac12 has quit [Quit: bye]
srinik has quit [Ping timeout: 480 seconds]
nothorseface has quit []
srinik has joined #aarch64-laptops
alfredo has joined #aarch64-laptops
srinik has quit [Ping timeout: 480 seconds]
nothorseface has joined #aarch64-laptops
echanude has joined #aarch64-laptops
nothorseface has quit [Ping timeout: 480 seconds]
<robclark>
JensGlathe[m]: for sure the gpu is different (3 SP vs 6 SP), I suspect various OPP tables will be different and a lot of other various x1e80100.dtsi type things.. you could try disabling ICC and DRM_MSM and see how far you get, but I suspect we'll need patches from qc
<robclark>
probably the part is pin compatible and "identical" from OEM/ODM PoV but that doesn't mean there aren't differences in core dtsi
derzahl has quit [Ping timeout: 480 seconds]
derzahl has joined #aarch64-laptops
exeat has quit [Ping timeout: 480 seconds]
alfredo has quit [Read error: Connection reset by peer]