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
<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 😔