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)
<clover[m]>
6.0.7-0-x13s booting and seems to work well
iivanov has quit [Read error: Connection reset by peer]
iivanov has joined #aarch64-laptops
_alice has quit [Read error: No route to host]
ardb has quit [Write error: connection closed]
jbowen has quit [Read error: No route to host]
jhugo___ has quit [Read error: No route to host]
dianders has quit [Read error: Connection reset by peer]
jhugo___ has joined #aarch64-laptops
_alice has joined #aarch64-laptops
jbowen has joined #aarch64-laptops
dianders has joined #aarch64-laptops
ardb has joined #aarch64-laptops
<Caterpillar>
I think Linaro's Debian for Thinkpad X13s consumes a ton of energy, do you agree with me?
alpernebbi has quit [Remote host closed the connection]
alpernebbi has joined #aarch64-laptops
alpernebbi has quit [Quit: alpernebbi]
Evaia631 has quit [Quit: Hack the Gibson]
Evaia631 has joined #aarch64-laptops
alpernebbi has joined #aarch64-laptops
Sally[m] has joined #aarch64-laptops
<rfs613>
Caterpillar, fairly sure there is no power management right now...
jhovold has quit [Ping timeout: 480 seconds]
xroumegue has quit [Ping timeout: 480 seconds]
<steev>
there's *some* powermanagement, the stuff we get for free, i think
<steev>
but yeah, it definitely currently consumes more than it should
travmurav[m] has quit [Write error: connection closed]
ungeskriptet[m] has quit [Write error: connection closed]
Guest603 has quit [Write error: connection closed]
underpantsgnome[m] has quit [Write error: connection closed]
fevv8[m] has quit [Write error: connection closed]
robertmader[m] has quit [Write error: connection closed]
szclsya[m] has quit [Write error: connection closed]
AlexMarty[m] has quit [Remote host closed the connection]
clover[m] has quit [Write error: connection closed]
NomadNaomie[m] has quit [Remote host closed the connection]
mahmoudajawad[m] has quit [Write error: connection closed]
EricCurtin[m] has quit [Write error: connection closed]
Sobek[m] has quit [Remote host closed the connection]
harvestz[m] has quit [Write error: connection closed]
psydroid[m] has quit [Write error: connection closed]
Sally[m] has quit [Remote host closed the connection]
Leandro[m] has quit [Write error: connection closed]
luxio_39[m] has quit [Write error: connection closed]
mothenjoyer69 has quit [Write error: connection closed]
jenneron[m] has quit [Write error: connection closed]
cmeerw[m] has quit [Write error: connection closed]
frytaped[m] has quit [Write error: connection closed]
Dylanger has quit [Write error: connection closed]
harvests[m] has quit [Write error: connection closed]
danielt has quit [Write error: connection closed]
davidebeatrici[m] has quit [Write error: connection closed]
qzed has quit [Write error: connection closed]
ajhalaney[m] has quit [Write error: connection closed]
arisu has quit [Write error: connection closed]
Manis[m] has quit [Write error: connection closed]
quinine has quit [Write error: connection closed]
Lucy[m] has quit [Write error: connection closed]
steevdave[m] has quit [Write error: connection closed]
amstan has quit [Write error: connection closed]
ajhalaney[m] has joined #aarch64-laptops
akaWolf has joined #aarch64-laptops
<akaWolf>
hi, guys! can you say me what is the current status of support of x13s laptop by Linux kernel?
<steev>
there's some support, and other not support
<steev>
big missing bits are gpu and audio
<akaWolf>
what's the problem with audio? and perspectives?
<steev>
perspectives?
<steev>
not sure what you're asking there
<akaWolf>
yeah, plans, ideas, etc
<steev>
the audio currently is written, but not all the bits are public
<steev>
and it doesn't work for me and we don't know why
<steev>
it's something on the alsa side though
<akaWolf>
I see... well I guess when I'll be able to get those laptop you will already figure out the issue
<steev>
maybe :)
<steev>
the plan is definitely to get as much supported as possible though
<akaWolf>
is there a problem to make last bits public?
<steev>
they will be, once the issues are sorted
<akaWolf>
ah I see, okay, so there is no licensing issues
<steev>
it's less "private because people hate open source" and more "private because it doesn't work yet and don't need developers being hounded by end users about when its gonna work"
<akaWolf>
yeah I understand
<steev>
lenovo are fairly on board with everything (from my understanding)
<steev>
and have/do work on things being released with their legal and such
<akaWolf>
yeah but just a few models have Linux sertification (IIUC it's internal one)
<steev>
this won't afaik, have linux certification; at least, not for a long time
iivanov has quit [Quit: Leaving...]
<akaWolf>
I see there are few guys from linaro. is it nice company?
<akaWolf>
someone from Saint Petersburg office?
<ndec>
i think linaro is nice. but maybe i am biased :)
<ndec>
for the audio bits, we really need to get it to work.. i know it's working for srinik since i had meetings with him! srinik can you please share detailed instructions for some initial audio support?
<akaWolf>
maybe in the future when I decide to return to embedded I'll try to apply. didnt know about StP office.
<ndec>
linaro has 'no office', it's a remote first company.
<akaWolf>
ah I see, just saw someone from Linaro who work in Saint Petersburg. okay
<akaWolf>
steev: just for information, how audio doesnt work for you?
<akaWolf>
some errors, registers not initialized, etc
<steev>
alsaucm listcards was just saying it couldn't load configuration hw:0
<steev>
ndec: now that the audio stuff is mostly posted to the ml (i think only the dtb parts and defconfig are missing), i can try to throw them in, i've got older revisions here
<steev>
error: failed to import hw:0 use case configuration -2
ajhalaney[m] has quit [Write error: connection closed]
<akaWolf>
why do you think the problem is with alsa and not with driver?
ajhalaney[m] has joined #aarch64-laptops
akaWolf has quit [Ping timeout: 480 seconds]
root_ has joined #aarch64-laptops
root_ is now known as akaWolf0
<akaWolf0>
sorry. I mean why do you think the problem with alsa userspace/kernelspace? and not with somethind underlying?
akaWolf has joined #aarch64-laptops
<akaWolf0>
I guess we need to figure out what syscall results in -2 error
<steev>
because of discussions with the dev
<steev>
alsa listcards working on an entirely unrelated device means absolutely nothing
<akaWolf0>
I see. sorry I dont have a context.
akaWolf has quit [Ping timeout: 480 seconds]
akaWolf has joined #aarch64-laptops
SSJ_GZ has quit [Ping timeout: 480 seconds]
akaWolf has quit [Ping timeout: 480 seconds]
akaWolf has joined #aarch64-laptops
<steev>
to be fair, i don't either. there's a lot of moving parts with alsa, and where it's working is debian sid, but i'm on stable; i probably should switch to sid, but if i do, i'll end up hitting https://gitlab.gnome.org/GNOME/mutter/-/issues/2398
<ndec>
steev: argh. i thought about asking you last week about the mutter bug.. and forgot.. so it's still there, right?
<steev>
ndec: afaik, yeah
<steev>
i *think* leezu is the one who hit it first (it doesn't happen in stable debian because we're still pre-atomic stuff in mutter)
<ndec>
yeah, that i remember.
<ndec>
has it been confirmed that it happens only on snapdragon? my x86 laptop runs fine with latest gnome and my usb monitor at least.
<steev>
i don't have any other arm devices worth testing it on - i'm hoping my rock5 shows up soon