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)
booda has quit []
<steev>
hm, that seems slow, but mine is off at the moment so i can't check the time it takes me
<steev>
assuming you're just using distro_defconfig?
<rfs613>
yep, exactly per the readme ;-)
* rfs613
does not expect to build kernels often... it was more of a curiosity to see how practical it is.
<steev>
the only chip that really approaches/passes x86 is the m1 right now
<steev>
it ain't gonna beat a thread ripper though
<HdkR>
Technically since AMD hasn't released a Zen3 threadripper, the M1 beats current thread ripper in single threaded tasks :P
<rfs613>
so the really funny part about today's success with wifi on my c630... is that i have a shiny new x86 laptop arriving tomorrow...
<rfs613>
i guess its kind of murphy's law... right now the c630 is behaving fantastic ;-)
<steev>
the funny part is having these laptops... and no where to go
<steev>
but my pto request was approved today, so my ticket purchase isn't gonna go to waste
<steev>
i also have more powerful laptops, but still prefer the c630 just because it's so light
<steev>
rfs613: fwiw, re: losing touchpad after suspend, sometimes if you just close the c630 and open it back up, you get it back too, so there's that
<rfs613>
good to know, thanks
<steev>
also just checked mine too and yeah, roughly 51 minutes
FizzBuzz has quit []
<HdkR>
A good presentation at HotChips today about Neoverse N2. Wish we would get real laptop SoCs with it :(
<steev>
ask them for it
<HdkR>
*Wiggles fingies*
<HdkR>
Gimme please
<robclark>
let me just punch in a few numbers into my SoC-o-matic... oh, wait..
<HdkR>
But that requires getting a capture, that's a lot of work :D
<robclark>
well, I mean, I guess a capture isn't required but having a way to repro a bug does increase the odds of someone doing something about it
<robclark>
(ie. get a capture)
<HdkR>
Difficult repro steps sadly reduce the chance of someone tinkering with it. I'll probably get a capture soonish
<robclark>
captures that repro are defn useful considering that your setup might be hard to replicate ;-)
<HdkR>
I mostly just need to document how to get a capture for myself. I can never remember the magic environment variables to do it
<HdkR>
There we go, wrote some documentation to make my life easier
<robclark>
that is why I write (and also why I forget to write) docs.. so I can remember things :-P
<HdkR>
Documentation where I can copy and paste old commands is the best
<HdkR>
Steam updates, breaks something, copy and paste commands and it works again, yay
<robclark>
documentation for me, when it comes to just remembering a sequence of cmds and/or env vars, tends to turn into scripts for me
<robclark>
see `~/bin/hud.sh` for how to drive GALLIUM_HUD :-P
<HdkR>
oh, I have that slapped in to a FEX configuration file. So I know if an application is running under FEX or not :D
<HdkR>
Can set environment variables independently of what is provided in the real envirnoment
<HdkR>
Oop! It's not a Freedreno bug. It's a FEX bug :D
macc24 has quit [singleton.oftc.net synthon.oftc.net]
spawacz has quit [singleton.oftc.net synthon.oftc.net]
EmersonCardoso[m] has quit [singleton.oftc.net synthon.oftc.net]
sporos11[m] has quit [singleton.oftc.net synthon.oftc.net]
amstan has quit [singleton.oftc.net synthon.oftc.net]
trench has quit [singleton.oftc.net synthon.oftc.net]
kholk[m] has quit [singleton.oftc.net synthon.oftc.net]
fevv8[m] has quit [singleton.oftc.net synthon.oftc.net]
strongtz[m] has quit [singleton.oftc.net synthon.oftc.net]
MatrixTravelerbot[m] has quit [singleton.oftc.net synthon.oftc.net]
agraf has quit [singleton.oftc.net synthon.oftc.net]
Esmil has quit [singleton.oftc.net synthon.oftc.net]
iivanov has quit [singleton.oftc.net synthon.oftc.net]
qzed[m] has quit [singleton.oftc.net synthon.oftc.net]
exit70[m] has quit [singleton.oftc.net synthon.oftc.net]
HdkR has quit [singleton.oftc.net synthon.oftc.net]
pg12_ has quit [singleton.oftc.net synthon.oftc.net]
tomeu has quit [singleton.oftc.net synthon.oftc.net]
maz has quit [singleton.oftc.net synthon.oftc.net]
calebccff has quit [singleton.oftc.net synthon.oftc.net]
jhugo has quit [singleton.oftc.net synthon.oftc.net]
steev has quit [singleton.oftc.net synthon.oftc.net]
shawnguo has quit [singleton.oftc.net synthon.oftc.net]
vkoul has quit [singleton.oftc.net synthon.oftc.net]
pundir has quit [singleton.oftc.net synthon.oftc.net]
ndec has quit [singleton.oftc.net synthon.oftc.net]
unixsmurf has quit [singleton.oftc.net synthon.oftc.net]
CosmicPenguin has quit [singleton.oftc.net synthon.oftc.net]
samueldr has quit [singleton.oftc.net synthon.oftc.net]
mattst88 has quit [singleton.oftc.net synthon.oftc.net]
broonie has quit [singleton.oftc.net synthon.oftc.net]
arnd has quit [singleton.oftc.net synthon.oftc.net]
aarch64-bridge has quit [singleton.oftc.net synthon.oftc.net]
dianders has quit [singleton.oftc.net synthon.oftc.net]
gwolf has quit [singleton.oftc.net synthon.oftc.net]
rfs613 has quit [singleton.oftc.net synthon.oftc.net]
bamse has quit [singleton.oftc.net synthon.oftc.net]
CosmicPenguin has joined #aarch64-laptops
samueldr has joined #aarch64-laptops
strongtz[m] has joined #aarch64-laptops
arnd has joined #aarch64-laptops
broonie has joined #aarch64-laptops
aarch64-bridge has joined #aarch64-laptops
macc24 has joined #aarch64-laptops
iivanov has joined #aarch64-laptops
vkoul has joined #aarch64-laptops
kholk[m] has joined #aarch64-laptops
qzed[m] has joined #aarch64-laptops
fevv8[m] has joined #aarch64-laptops
EmersonCardoso[m] has joined #aarch64-laptops
sporos11[m] has joined #aarch64-laptops
exit70[m] has joined #aarch64-laptops
amstan has joined #aarch64-laptops
MatrixTravelerbot[m] has joined #aarch64-laptops
trench has joined #aarch64-laptops
HdkR has joined #aarch64-laptops
steev has joined #aarch64-laptops
tomeu has joined #aarch64-laptops
ndec has joined #aarch64-laptops
agraf has joined #aarch64-laptops
gwolf has joined #aarch64-laptops
Esmil has joined #aarch64-laptops
pg12_ has joined #aarch64-laptops
maz has joined #aarch64-laptops
rfs613 has joined #aarch64-laptops
dianders has joined #aarch64-laptops
unixsmurf has joined #aarch64-laptops
bamse has joined #aarch64-laptops
shawnguo has joined #aarch64-laptops
calebccff has joined #aarch64-laptops
spawacz has joined #aarch64-laptops
mattst88 has joined #aarch64-laptops
jhugo has joined #aarch64-laptops
pundir has joined #aarch64-laptops
booda has joined #aarch64-laptops
booda has quit []
<robclark>
HdkR: well, you got the first letter correct at least :-P
<HdkR>
:D
<macc24>
what is the difference between freedreno and fex anyway
<robclark>
it's all just a bunch of codes :-P
<macc24>
freedreno's got a compiler - fex has a compiler, freedreno runs on arm64 machines - fex runs on arm64 machines
booda has joined #aarch64-laptops
<HdkR>
FEX runs under an x86-64 environment, Freedreno runs under an x86-64 environment
<HdkR>
Basically the same
macc24 has quit [Ping timeout: 480 seconds]
booda has quit []
<rfs613>
well, new x86 laptop arrived a few hours ago, but I haven't had any desire to open the box yet ;-)
<steev>
what did you get?
<steev>
re: weight... i really like the lenovo x1 carbons as they're lightweight, but pricey
<HdkR>
Dell XPS 13 is also pretty good in that regard
<robclark>
as far as x86 laptops goes, xps13 is a pretty good one
macc24 has joined #aarch64-laptops
<gwolf>
I had a XPS 13, many years ago (~2007 IIRC). It was a sweet machine, but as heavy as it gets
<HdkR>
13 years of innovation lets them change that
<gwolf>
I guess!
<macc24>
i'm actually piecing together a thinkpad t400 for all my x86 needs lol
<macc24>
i need to be able to use ms access to pass next grade and i am not risking failing if average grade is 0.08 lower than i thought it would be(i promise this happened)
Wizzard has joined #aarch64-laptops
<rfs613>
steev: you guessed it, x1 carbon, i7, 16gb
<steev>
nice
<steev>
which display though?
<steev>
i ended up selling mine because i got the 4K display and it ghosts so much :(
<steev>
and lenovo considers it "fine"
<rfs613>
1920x1200
<rfs613>
4k is wasted at 14" size, i can't see the pixels anyhow
<steev>
i more got it for linux testing of 4K
<steev>
but with the ghosting... just no
<rfs613>
i leave that to the kids ;-)
<steev>
it's part of my job :P
<rfs613>
fair enough...
<HdkR>
<3 my XPS 13's 4k screen
<gwolf>
uff
<gwolf>
FWIW, I really enjoy having a FHD (1920x1080) laptop instead of the 1366x768 I had until now... that feels cramped
<gwolf>
but yes, 13"/14" is a bit too much for that
<gwolf>
Now OTOH, for my desktop... I love my 3840x2160 monitor :-]
<steev>
yeah, 1366 just doesn't cut it these days
<steev>
unless you don't multitask
<rfs613>
yeah, that's one of the reasons I stopped using my good old x201 laptop
Wizzard has quit [Remote host closed the connection]
<gwolf>
Even using i3 / sway... my thoughts are too large for the screen :-]
booda has joined #aarch64-laptops
<steev>
i threw some things that are coming down the stable 5.13 pipeline into my 5.12 kernel and pushed it
<steev>
have tested it here, nothing seems to break at least
booda has quit [Remote host closed the connection]
<gwolf>
steev: I understand Debian's 5.13 kernel is in experimental, and probably it will enter unstable soonish
<steev>
gwolf: yeah but 5.13 on the c630 has an issue that someone is still in the middle of tracking down
<gwolf>
steev: I guess installing a mainline kernel will clobber some of your additions. Should I mark the kernel as a "hold" package? Or do you expect mainline to work in the C630 decently (FSVO)?
<steev>
well, it doesn't install linux-image-arm64 so it shouldn't pull in the debian kernel
<steev>
once the fbcon issue is tracked down and a patch provided and i test it, i'll probably fork the debian linux repo and apply it
<steev>
along with the other c630 patches
<gwolf>
OK, great to hear this!
<steev>
the reason i've stuck with 5.12 instead of on 5.11 is because of networking changes that came in 5.12 that i want for kali
unixsmurf has quit []
unixsmurf has joined #aarch64-laptops
booda has joined #aarch64-laptops
<steev>
oof
<steev>
just noticed debian leaves it at config_hz_250
<steev>
it's 2021 :(
<steev>
shawnguo: have you had a chance to go back and take a look at why enabling the crypto test causes kernel panic?
<robclark>
hmm, this is a new one (after rebasing kernel).. anyone seen this before:
<robclark>
aarch64-linux-gnu-ld: .init.data has both ordered [`__patchable_function_entries' in init/main.o] and unordered [`.meminit.data' in mm/sparse.o] sections
<steev>
i have not see that
robclark has quit []
robclark has joined #aarch64-laptops
<steev>
gwolf: ugh, looking at the debian config there are so so many qcom options not enabled that will need to be
<gwolf>
steev: Usually the kernel maintainers are quite amenable to adopting config changes (specially if they can be expressed in a modular way)
<gwolf>
and specially if they are justified
<steev>
yeah, i know they are but, they are not a fan of anything that isn't already upstreamed (in -next)
<steev>
hopefully bamse gets permission to post the battery stuff for sc8180x and we can do battery stuff for c630 properly after
<steev>
and get it posted up and accepted
<gwolf>
right - I meant because you were "complaining" about config_hz and things like that..
<steev>
oh, that... yeah
<steev>
those options are =y afaik, there's no runtime choosing