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
Evaia63101 has quit [Quit: Hack the Gibson]
Evaia63101 has joined #aarch64-laptops
Evaia63101 has quit [Quit: Hack the Gibson]
Evaia63101 has joined #aarch64-laptops
<steev>
even on the mini iso?
matalama_ has joined #aarch64-laptops
matalama has quit [Ping timeout: 480 seconds]
matalama_ has quit [Quit: Reconnecting]
matalama has joined #aarch64-laptops
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
<push>
hexdump0815: awesome! thanks! can grub understand a dts file? or is it mandatory to compile it?
alfredo has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
suihkulo1ki has joined #aarch64-laptops
suihkulokki has quit [Read error: Connection reset by peer]
ema has quit [Read error: Connection reset by peer]
ema has joined #aarch64-laptops
alfredo has quit [Remote host closed the connection]
alfredo has joined #aarch64-laptops
alfredo1 has joined #aarch64-laptops
alfredo has quit [Read error: Connection reset by peer]
<ema>
so basically the netboot image has working display but no firmware, while netinst has broken display but all firmware :)
<ema>
this should be fixed with the next kernel upload, and netinst will have both display and firmware
alfredo has quit [Ping timeout: 480 seconds]
hexdump01 has quit []
hexdump0815 has joined #aarch64-laptops
<hexdump0815>
push: the kernel needs a compiled dtb - if you are not familiar with how all this works, then please be very careful
<hexdump0815>
push: i have no idea which quality this dts has and you can toast your hardware with a wrong dts in the worst case - you have been warned :)
matalama_ has quit [Quit: Connection closed for inactivity]
<push>
hexdump0815: :O i had no idea a bad dtb could toast your hardware, how common is that?
<push>
owc[m]: thanks for submitting that!
alfredo has joined #aarch64-laptops
ungeskriptet has joined #aarch64-laptops
matalama_ has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
systwi has quit [Read error: Connection reset by peer]
systwi has joined #aarch64-laptops
<clover[m]>
steev: 3 days late but 6.5.4 boots fine. noticed we got some video camera/capture options in the kernel, thats exciting
<steev>
cam stuff is still in the works and, afaik, requires userland stuff too
matalama_ has quit [Quit: Connection closed for inactivity]
hexdump0815 has quit [Quit: WeeChat 1.9.1]
hexdump0815 has joined #aarch64-laptops
<hexdump0815>
push: i think it is not very likely that the hardware will break, but it is something to keep in mind as a possibility
<hexdump0815>
push: the dts defines the voltage regulators and their voltages and worst case voltages might be sent to chips above of what they like
<hexdump0815>
push: also some wiring up of fuctionality is done in the dts, also there something might end up very wrong
<hexdump0815>
push: it is unlikely to happen ,but it is definitely something to be aware of when playing around with this stuff
<push>
hexdump0815: I hadn't considered that, but it makes sense. I will probably still give it a try when i get the time, or do you think it is a fruitless effort?
<push>
I used your framework to build a vanilla 6.5.4 kernel for the novago, it works pretty much identical to your patched 6.1.
<push>
Did the x13s get more interest, or did lenovo publish more data? trying to figure out why some laptops qre made to work while others don't.
<hexdump0815>
push: to me the thread i posted from back then about the go 5g dts looked like it should work
<hexdump0815>
push: re novago - whyt i have in my image is essential what is in mainline - the intersting part to get more stuff working
<hexdump0815>
push: i think the pmos guys have some more stuff working on msm8998/sdm835, so it should be possible to maybe also get things like cpu freq scaling, gpu, wifi etc. working on the novago as well somehow
<hexdump0815>
push: re which laptop gets how much support - as those devices nowadays need a lot of complex work to get supported there is either some sponsor required to support such work or someone with a lot of passion
<hexdump0815>
push: in 2019 there was some interest in arm laptops by red hat, canonical etc. i think which resulted in a push of developemnt for the sdm835 and sdm850 devices (novago, c630 etc.) which slowed down massively a few months later and the topic did not come up again from those companies afterwards
<push>
yeah! I remember reading about that, and I was excited so I bought one thinking that it will work "any day now"
<hexdump0815>
push: c630 was still brought forward quite a bit over time by some of the usual suspects of this channel :) ... nobody with the proper skills cared about sdm835 anymore, so it got lost in its half supported state
<push>
even microsoft abandoned it, it will never run windows 11
<push>
which is a shame cause its a nice thing
<hexdump0815>
now there is quite a bit of momentum behind the x13s and lenovo/qcom seems to at least a bit support that effort resulting in maybe the first quite well supported arm woa laptop
<push>
and I am very happy to see that :)
<push>
i wouldnt know the first thing about making the hardware work, no matter how passionate I am about it, so I'm reliant on others
<hexdump0815>
lets see, maybe even sdm835/sdm850 will get a bit more love once win10 support ends and those devices are otherwise paperweights only :)
<hexdump0815>
i think its a long term learning journey - i have learned quite a bit about that over time and maybe at some point it helps to get the novago a step further
<push>
I have two of them, I dont even have that much paper that needs held down xD
<hexdump0815>
steve is a good example for that: from just trying to use the c630 in the beginning to now doing a lot of x13s tree integration work and first mainline kernel patches an review work over a few years
<hexdump0815>
sadly for most of the woa laptops there is close to no documentation available and the windows/acpi info is not reliable enough for many things, i.e. moving on requires quite a bit of reverse engineering to make systems like the 7c galaxy book go and others fully useable
<push>
yeah, he's been helping me, im starting to learn who does what, ive been checking in on this project for years, i only recently decided i should take matters into my own hands
<hexdump0815>
the situation looks much better on the arm chromebook side where google makes sure that there is proper mainline support for all the devices (to save cost for maintaining them) and they even have things like working kvm :9
<push>
I have a 7c galaxy book too, its kinda funny the stuff that works on it doesnt work on the novago, and the stuff that works on the novago doesnt work on the galaxy book
<push>
i see you have a bunch of chromebooks, but most of them only have like 4Gb of memory
<hexdump0815>
so maybe time to cut them in half and glue them together to get a fully working one :)