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
enyalios_ has joined #aarch64-laptops
enyalios has quit [Ping timeout: 480 seconds]
enyalios_ is now known as enyalios
<Melody91> I've been trying to see if there's any progress on the WDK 2023 front. It looks like https://github.com/merckhung/linux_ms_dev_kit is a potential go!
todi has joined #aarch64-laptops
todi1 has quit [Ping timeout: 480 seconds]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
alfredo has joined #aarch64-laptops
alfredo1 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
laine has quit [Ping timeout: 480 seconds]
<steev> possibly? it would be nice if they submitted stuff to the mailing lists though so people didn't have to dig through github
alfredo has quit [Read error: Connection reset by peer]
jkm has quit [Remote host closed the connection]
laine has joined #aarch64-laptops
enyalios_ has joined #aarch64-laptops
enyalios has quit [Ping timeout: 480 seconds]
hexdump01 has quit []
hexdump0815 has joined #aarch64-laptops
<hexdump0815> Melody91: i think the latest state regarding wdk 2023 can be found here: https://github.com/jglathe/linux_ms_dev_kit/discussions/1
<hexdump0815> Melody91: it seems to be close to the x13s state as it seems to share quite a bit of the hardware setup
<Melody91> Hey! The https://github.com/jglathe/linux_ms_dev_kit/discussions/1#discussioncomment-6715205 looks hopeful for making it not as difficult to rebase on other kernels.
<Jasper[m]> <Melody91> "Hey! The https://github.com/..."; <- There's someone on linux-surface and on the aarch64-laptops repo doing similar stuff
<Jasper[m]> And fetching the firmware from the windows partition is far from ideal because Microsoft has been neglecting updating it a bit
<Jasper[m]> Jasper[m]: okay the user is active in both repo's so that's good
alfredo has joined #aarch64-laptops
<Melody91> I was originally looking at linux-surface but they were having a problem making a device tree.
<Melody91> Actually, I sorta wonder if one could use the dtb from jglathe's GitHub with linux-surface.
fvogt has joined #aarch64-laptops
heapify has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
heapify is now known as heapheap
<lvrp16> The big dealbreaker for me is that it might be stuck at EL1 so no virtualization. Only suitable as a compile machine. The 32GB is useless.
<hexdump0815> lvrp16: i think all woa devices have no kvm support
<lvrp16> hexdump0815: Johan said it was a firmware limitation from Qualcomm's UEFI implementation.
alfredo has joined #aarch64-laptops
<travmurav[m]> s/limitation/deliberate design choice/
alfredo has quit [Quit: alfredo]
heapheap has quit []
<Dylanger> Does anyone know if it's possible to get around depthcharge's 32MB limit for it's kernel?
enyalios has joined #aarch64-laptops
enyalios_ has quit [Ping timeout: 480 seconds]
alfredo1 has joined #aarch64-laptops
alfredo1 is now known as alfredo
alfredo1 has joined #aarch64-laptops
alfredo has quit [Ping timeout: 480 seconds]
alfredo1 is now known as alfredo
<hexdump0815> Dylanger: iirc newer systems are supposed to allow larger kernel partitions - maybe trogdor and newer or so - i think robclark mentioned that once
* robclark is using the two original 32MB kernel partitions
<hexdump0815> Dylanger: but in theory it should be possible to live with the 32mb limit if kernel and initrd are getting heavily compressed - i'm doing that all the time on my linux chromebooks and still have some room left :)
<hexdump0815> Dylanger: i see the 16mb limit on 32bit armv7l chromebooks as much more complicated as with that its not really possible to use initrd
<hexdump0815> Dylanger: but on the other hand - for all of the 32bit chromebooks there is some kind of u-boot around, which can be used chainloaded to load an initrd - so no real problem there neither
<Dylanger> Thank you for response
<Dylanger> Mainline Linux doesn't boot MediaTek cherry 😔
<hexdump0815> robclark: sorry - found the source of that information in my notes and alpernebbi once said that: https://oftc.irclog.whitequark.org/aarch64-laptops/2022-02-18#30644059
heapify has joined #aarch64-laptops
alfredo1 has joined #aarch64-laptops
alfredo1 has quit []
alfredo has quit [Ping timeout: 480 seconds]
heapify has quit [Quit: heapify]
heapify has joined #aarch64-laptops
heapify has quit []
matalama_ has joined #aarch64-laptops
<jenneron[m]> <hexdump0815> "Dylanger: i see the 16mb limit..." <- still depends on kernel config and compression and a bit on architecture
<jenneron[m]> exynos chromebooks are limited to 8M, we have initramfs in pmOS and we have FDE support
Kelsar has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
Kelsar has joined #aarch64-laptops
Kelsar has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
Kelsar has joined #aarch64-laptops
matalama_ has quit [Quit: Connection closed for inactivity]
<Dylanger> I've managed to get a kernel + initrd with dracut for LUKs
<Dylanger> In the 32MB window
<Dylanger> You could cut down further via disabling KSYMs
<Dylanger> But yeah, mainline won't boot for MT8195/cherry 😞
<Dylanger> I'll have a look with Suzy
<agl7> Good evening! ;-) (In Central Europe is it 10:24 pm)
hexdump0815 has quit [Quit: WeeChat 1.9.1]
hexdump0815 has joined #aarch64-laptops
mcbridematt has quit [Quit: Leaving]