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)
hightower3 has joined #aarch64-laptops
hightower2 has quit [Ping timeout: 480 seconds]
agl7-Galaxy has quit [Remote host closed the connection]
agl7-Galaxy has joined #aarch64-laptops
agl7-Galaxy has quit [Remote host closed the connection]
agl7-Galaxy has joined #aarch64-laptops
<steev>
jhovold: aren't your audio patches from srini still v1 not v2?
agl7 has quit [Remote host closed the connection]
hexdump01 has joined #aarch64-laptops
hexdump0815 has quit [Ping timeout: 480 seconds]
Lucanis0 has joined #aarch64-laptops
Lucanis has quit [Ping timeout: 480 seconds]
svarbanov has joined #aarch64-laptops
<jhovold>
steev: they are effectively v2 backported to 6.4
<jhovold>
I'm still carrying the patch moving runtime pm enable though as a workaround for another audio bug that otherwise breaks audio every five boots or so
<jhovold>
It changes the timimg enough to avoid it, srinik is trying to find a fix
svarbanov has quit [Ping timeout: 480 seconds]
hightower3 has quit []
<jhovold>
robclark: are the fixes for the firefox video/webgl crases making their way into the stable mesa releases 23.1.x? Looks like they are still not in 23.1.3.
moa5505 has joined #aarch64-laptops
<moa5505>
Hello everyone, I want to try linux on a Ideapad 5g (which is a 8cx gen2 device and should be quite similar to a Yoga 5G). Any documentation or advices ? I tried the standard arm Debian image, but it didn't boot
agl7-Galaxy has quit [Ping timeout: 480 seconds]
moa5505 has quit [Remote host closed the connection]
agl7-Galaxy has quit [Remote host closed the connection]
agl7-Galaxy has joined #aarch64-laptops
<steev>
calebccff: indeed that does seem to help as well
<eric_engestrom>
robclark, jhovold: the commits in !23324 are all fixes and self-contained, so they make sense to backport; all the commits applied cleanly and compiled fine, so provided the CI doesn't find any regression, they'll be in 23.1.4 :)
<robclark>
eric_engestrom: thx
<jhovold>
eric_engestrom: thanks!
<qzed>
jhovold: thanks for the review!
<qzed>
jhovold: I'll try to answer later today, but I'm not sure if I can find the headspace...
<qzed>
jhovold: if I can't do it today it might take some time... I'm moving/preparing a new flat and things are rather hectic right now
<exeat>
AFAICT there's a commit to disable pauth for the kernel, but the cpu feature is still visible to userspace...
<exeat>
Then arm64.nopauth completes the job and nobody needs to hurt themselves with gdb's target.xml :)
hexdump01 has quit [Quit: WeeChat 1.9.1]
hexdump0815 has joined #aarch64-laptops
<hexdump0815>
moa5505: (maybe you read this offline) - jenneron[m] did get his flex 5g working recently, maybe he has some bootable image around somewhere for it for you to start from for your ideapad 5g
<jhovold>
qzed: ah, yeah, i saw you mentioning that in the logs here
<jhovold>
i wanted to comment on 4/4 but didn't find the time today, i know have at least a couple of comments on that one too, nothing major
<jhovold>
do you think you'll be able to work on it to get it into 6.6 despite the moving?
<jhovold>
robclark, exeat: thanks for the heads up, I'll look into disabling pauth properly in my wip branches going forward
<jhovold>
was hoping we'd have a fixed fw before everyone starts adding arm64.nopauth to their command lines and just leave it there forever
<konradybcio>
jhovold most of 8280 devices are probably EOL by noc :P
<konradybcio>
now*
<jhovold>
konradybcio: you mean there'll be no fixed fw wrt pauth? rumour has it there may be...
<konradybcio>
I'd hope there would be.. but companies have a track record of not updating firmware beyond whatever tag the device released with
<qzed>
jhovold: I will try, I should have time on the evenings of next week. Not sure if i'll have proper internet yet, but I should be able to work off of my mobile one
<robclark>
which fw is needed for the pauth stuff?
<konradybcio>
tz
* robclark
has no idea about pauth
<robclark>
ahh, tx
<konradybcio>
it's always tz, innit :P
<jhovold>
qzed: sounds good, just let me know if there's anything I can do to help. I assume you may have written that strscpy helper already, for example?
<robclark>
oh, I suppose pauth is pointer authentication?
<konradybcio>
y
<robclark>
ok.. makes sense that that is a thing gdb would care about
<qzed>
<jhovold> "qzed: sounds good, just let me..." <- I have, I haven't gotten around to fully test it yet though, I'll try to do that later today then I can push things somewhere
<qzed>
jhovold: it's essentially the same thing as on the ml, with on static fix (I think the one you mentioned in your review is still missing) and strscpy instead of strlcpy
<qzed>
(and strscpy isn't fortified, I think fortifying the whole ucs2_string stuff is an opportunity for a follow-up series)
<qzed>
jhovold: feel free to take it over and make some changes, I'll probably not get to it until some time next week
<qzed>
unfortunately I still haven't had a detailed look at your comments, but since you mentioned adding an extra device for qseecom:
<qzed>
v3 had something similar, but people wanted to keep the scm calls exclusively in qcom_scm and remove the need for a compatible, so I scrapped that
<qzed>
we can probably still add an extra device, but I'm not sure if we can get around having some bootstrapping code in qcom_scm