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)
<steev>
gwolf: so, it's really just git clone https://github.com/steev/linux -b linux-5.14.y --depth 1 (or leave the depth off if you wanna play around with the commits); cd linux; make distro_defconfig; make bindeb-pkg
<steev>
that's what i do here
<gwolf>
OK, good!
<gwolf>
Dumb question: One of my ARM cores is happily building a new kernel. Most of the chip is just whistling idly
<gwolf>
Can linux be built with a -j 8 or so?
<gwolf>
(yes, this is my first kernel compile in several years)
<robclark>
yes, -j8
<robclark>
kernel build is pretty well parallelized
<gwolf>
OK. Well, I set it to build a while ago, and just as an excercise, I'll let it finish (to see te total time it takes)... but I'll later build with -j8
<gwolf>
yes, that's what I expected, and was half-surprised it's not a default choice
<gwolf>
but who am I to judge ;-)
<steev>
you can kill it and pass -j$(nproc)
<steev>
it will pick up where it left off with bindeb-pkg
<steev>
ugh, they still haven't backported the fix for qrtr in stable
<gwolf>
right, of course ;-) But as I said, I want to see how long it takes
<gwolf>
why? Cannot really tell you...
<steev>
you do you :)
<gwolf>
but well, the laptop will stay busy while I cook lunch
<gwolf>
I just want to compare empirically ;-)
<gwolf>
Do you know of any differences I should note between 5.12 and 5.14 (other than oooo shiny!) ?
<steev>
mostly the oooh shiny
<steev>
but also, 5.12 is eol, so 5.14 is still getting updates
<gwolf>
OK (-:
<gwolf>
Anyway, /me prepares food for the family. AFK !
<steev>
enjoy
iivanov has joined #aarch64-laptops
iivanov_ has joined #aarch64-laptops
iivanov has quit [Ping timeout: 480 seconds]
iivanov has joined #aarch64-laptops
iivanov__ has joined #aarch64-laptops
iivano___ has joined #aarch64-laptops
iivan____ has joined #aarch64-laptops
iivanov_ has quit [Ping timeout: 480 seconds]
iivanov has quit [Ping timeout: 480 seconds]
iivan____ has quit []
iivanov__ has quit [Ping timeout: 480 seconds]
iivano___ has quit [Ping timeout: 480 seconds]
<gwolf>
steev: your git is missing a file -- dt-bindings/power/qcom-aoss-qmp.h
<steev>
no
<steev>
i fucked up
<steev>
let me push
<gwolf>
thanks!
<steev>
remember the whole, getting better at testing thing :P
<gwolf>
hey, if this is the way I can contribute and help you, I'm happy to!
<steev>
i pulled in some f sibi's changes, but since the flex 5g isn't in the kernel, he didn't modify that
<steev>
and i didn't go through and make the changes to the dtsi yet, so i backed those patches out til i have some time to do it
<steev>
that also bumps to 5.14.6
<gwolf>
right, I guessed I could comment out the include, but that's usually prone to break the world if not done carefully
<steev>
nah, that would break too, not that it would matter too much since you're on c630 not flex :)
<gwolf>
right. Well, I'm doing a full clone, as I want to try to understand a bit what's your diff from upstream
<gwolf>
...a bit at least
<steev>
Your branch is ahead of 'origin/linux-5.14.y' by 42 commits.
<steev>
you can also just look at it in the github web interface :)
<steev>
for the most part it's, take the aarch64-laptops stuff, and then pull in various fixes on top of that
<gwolf>
meh, I'll have it locally
<steev>
which is me loading up patchwork for the msm mailing list, or sometimes freedreno
<gwolf>
it won't hurt
<gwolf>
(other than time... I'm geting bored of waiting)
<steev>
the only difference is what project/server i point at
<gwolf>
don't worry, I don't want to monopolize channel traffic... As you know, I am quite new in low-level-land, and I'm just peeking around...
<steev>
one thing i really dislike, for whatever reason, alsa-devel's patchwork webpage shows like 3 pages of patches, but the command line show like 69k patches and it takes centuries to load
<gwolf>
anyway, AFK again... Will tell you once the clone finishes, I build, and hopefully succeed
<steev>
should :) i did build test it before i pushed
derzahl has joined #aarch64-laptops
alpernebbi has quit [Remote host closed the connection]
alpernebbi has joined #aarch64-laptops
<derzahl>
hey goys
<derzahl>
steev: hows 5.14 working out?
<gwolf>
Right, I was about to ask the same ;-)
<gwolf>
steev: Built the new image... But it failed to boot :-( Have you tested it successfully?
<gwolf>
After some ~5 seconds, after the initial flicker when Linux sets up its console, the screen got solid-blue
<gwolf>
and AFAICT, the machine was non-responsive
<derzahl>
gwolf: on what hardware?
<gwolf>
C630
<derzahl>
ah, same
<derzahl>
compiling it now
<derzahl>
i havent used it for awhile. last i heard there was still trouble with 5.13
<derzahl>
is that running good now?
<steev>
gwolf: ah, that, just close the lid for about 5 seconds
<steev>
then open it back up
<steev>
that's an issue that upstream devs are still trying to track down
<gwolf>
Hah!
<gwolf>
Will do right now
<gwolf>
Only at first power up?
<steev>
yeah
<steev>
it doesn't happen every boot
<derzahl>
steev: so other than that, 5.14 is pretty solid?
<gwolf>
Happens consistently for me, I'd say
<steev>
gwolf: do you shove everything into the initramfs? i notice it seems to have to do with loading the gpu firmware early
<gwolf>
OK. I'm about to watch a movie with the kids, so it will have to wait for... tonight? tomorrow?
<gwolf>
will check
<steev>
derzahl: i'd say so, there are a few issues with boots here and there, but, overall pretty good
<derzahl>
nice
<steev>
a vanilla 5.14 has broken wifi though, because the patch *still* hasn't been backported, despite 2 releases of 5.14 since the break
<steev>
well, not backported, just applied
<steev>
i need to look into how to say, hey can we please apply this to stable
<derzahl>
is it getting to the point where we can just use the vanilla kernel? other than wifi, has most of the patches been incorporated?
<steev>
the only thing not still in vanilla are battery and backlight control
<steev>
things still not in*
<steev>
bamse may have figured out how to *actually* control the volume, so hopefully that fix comes