ChanServ changed the topic of #aarch64-laptops to: Linux support for AArch64 Laptops (Asus NovaGo TP370QL - HP Envy x2 - Lenovo Mixx 630 - Lenovo Yoga C630)
shawnguo5 has joined #aarch64-laptops
shawnguo5 is now known as shawnguo
<flowriser> I can see TUX, it works
<flowriser> So far so good, I pushed all I have to: https://github.com/SMFloris/acer-spin7-linux
<flowriser> Tomorrow I'll get started on making the keyboard work, then wifi/modem
iivanov has joined #aarch64-laptops
flowriser_ has joined #aarch64-laptops
flowriser has quit [Remote host closed the connection]
flowriser_ has quit []
flowriser has joined #aarch64-laptops
<flowriser> Is there a way to create a initrd file without using a VM for aarch64?
<rfs613> flowriser: you could use buildroot for example - or yocto if you prefer - or even just assemble the initrd manually (it's just a cpio archive with a certain compression)
<rfs613> a VM is not required at all - though some people like to use them for isolation purposes.
<steev> if it had 8gb, i'd consider it
Lucanis1 has quit []
Lucanis has joined #aarch64-laptops
<robclark> yeah, with 8GB it would be pretty nice.. but still, for the price is good.. I don't think I've seen the 4GB/64GB lazor for less than $349
<amstan> is the $100 worth the fiddling with device trees?
<amstan> no to mention potentially weird type c implementations. i'm using the framework laptop now and boy it's quite the downgrade to what i'm used to on chromebooks
<robclark> not to mention, lack of suzyq
<robclark> but would be nice to see upstream support for the 7c windows laptops as well..
iivanov has quit []
derzahl has quit [Remote host closed the connection]
flowriser has quit [Remote host closed the connection]
derzahl has joined #aarch64-laptops
flowriser has joined #aarch64-laptops
<steev> bamse: i'm not near my mail client that can send to the list, but https://patchwork.kernel.org/project/linux-arm-msm/patch/1642398248-21753-2-git-send-email-quic_c_sanm@quicinc.com/ - this patchset seems to break things horribly on the c630
<bamse> steev: it's applied already?
<steev> no, i pulled it in to test it
<steev> but it has your r-b
<steev> i'm not sure WHY it's breaking out
<bamse> okay, i guess it won't be picked up until next week...will you find a mail client before then?
<steev> probably yeah
<steev> breaking it*
<steev> boot suddenly becomes slow as shit, and the remote procs don't seem to work properly anymore?
<bamse> hmm, typical symptoms when someone drops a voltage rail or release some important bus vote...
<bamse> but i don't see why that would be, just from that change
<bamse> or was it the whole series?
<steev> The whole series is applied
<steev> i guess it's breaking the mdt loader?
<steev> maybe 6/6 where it keeps the interrupts during probe?
<steev> i'll play around with the set, and see if i can figure it out - i tried adding modprobe.blacklist=ipa and that only gets a wee bit further it seems
<bamse> i don't think that says there's a problem in ipa...i thin it says that ipa gets stuck doing an scm call
<steev> the boot after that, it got stuck in ext4lazyinit
<steev> so yeah
<steev> bamse: okay yeah, it's the 6th patch - the first 5 all boot, 6th patch kills it - https://patchwork.kernel.org/project/linux-arm-msm/patch/1642398248-21753-7-git-send-email-quic_c_sanm@quicinc.com/