millenialhacker has quit [Ping timeout: 480 seconds]
yuyichao has quit [Quit: Konversation terminated!]
kettenis_ has joined #asahi-dev
kettenis has quit [Ping timeout: 480 seconds]
kettenis has joined #asahi-dev
kettenis_ has quit [Ping timeout: 480 seconds]
kettenis_ has joined #asahi-dev
kettenis has quit [Ping timeout: 480 seconds]
turo has joined #asahi-dev
kettenis_ has quit [Ping timeout: 480 seconds]
<amarioguy>
btw quick question does m2 use AICv1 or v2?
<chadmed>
aic2
<amarioguy>
gotcha
Catyre_ has joined #asahi-dev
Catyre__ has joined #asahi-dev
Catyre has quit [Ping timeout: 480 seconds]
Catyre_ has quit [Ping timeout: 480 seconds]
pseigo_ has joined #asahi-dev
pseigo_ has quit [Ping timeout: 480 seconds]
off^ has joined #asahi-dev
pseigo_ has joined #asahi-dev
PhilippvK has joined #asahi-dev
pseigo has joined #asahi-dev
phiologe has quit [Ping timeout: 480 seconds]
Graypup_ has joined #asahi-dev
pseigo_ has quit [Ping timeout: 480 seconds]
pseigo has quit [Ping timeout: 480 seconds]
pseigo has joined #asahi-dev
off^ has quit [Ping timeout: 480 seconds]
off^ has joined #asahi-dev
kov has quit [Quit: Coyote finally caught me]
millenialhacker has joined #asahi-dev
ajxu2 has joined #asahi-dev
ajxu2 has quit []
millenialhacker has quit [Ping timeout: 480 seconds]
off^ has quit [Remote host closed the connection]
off^ has joined #asahi-dev
off^ has quit [Ping timeout: 480 seconds]
nicolas17 has joined #asahi-dev
millenialhacker has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
nicolas17 has quit [Quit: Konversation terminated!]
pseigo has quit [Quit: left]
pseigo has joined #asahi-dev
millenialhacker has joined #asahi-dev
<sven>
hm, no android phone or Bluetooth keyboards here. Guess I’ll just have to assume those will work ;)
jluthra has quit [Remote host closed the connection]
<sven>
I think I should be able to somehow test ACL and SCO with audio anyway
jluthra has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
the_lanetly_052__ has joined #asahi-dev
kettenis has joined #asahi-dev
kettenis has quit [Ping timeout: 480 seconds]
MajorBiscuit has joined #asahi-dev
CarlEkerot[m] has joined #asahi-dev
CarlEkerot[m] is now known as frys[m]
pseigo has quit [Quit: left]
pseigo has joined #asahi-dev
millenialhacker has joined #asahi-dev
off^ has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
kettenis has joined #asahi-dev
timokrgr has quit [Quit: User left the chat]
timokrgr has joined #asahi-dev
millenialhacker has joined #asahi-dev
the_lanetly_052__ has quit [Ping timeout: 480 seconds]
millenialhacker has quit [Remote host closed the connection]
nirya has joined #asahi-dev
millenialhacker has joined #asahi-dev
off^ has quit [Ping timeout: 480 seconds]
millenialhacker has quit [Ping timeout: 480 seconds]
millenialhacker has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
millenialhacker has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
kettenis has quit [Remote host closed the connection]
kettenis has joined #asahi-dev
nirya is now known as HELP
kettenis has quit [Remote host closed the connection]
HELP is now known as nirya
kettenis has joined #asahi-dev
timokrgr has quit [Quit: User left the chat]
millenialhacker has joined #asahi-dev
timokrgr has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
off^ has joined #asahi-dev
systwi has joined #asahi-dev
off^ has quit [Ping timeout: 480 seconds]
kov has joined #asahi-dev
the_lanetly_052__ has joined #asahi-dev
<marcan>
progress report queued up, but let's get a release out before that :)
<marcan>
did anyone test the new kernels?
kettenis has quit [Ping timeout: 480 seconds]
millenialhacker has joined #asahi-dev
pseigo has quit [Ping timeout: 480 seconds]
<jannau>
marcan: it boots on m1 max mb pro 14" and everything seemed to work
<jannau>
io-pgtable-dart change looks good but it got squashed into the suspend commit
millenialhacker has quit [Ping timeout: 480 seconds]
<mps>
I could try to rebuild and test on j293 this evening
<mps>
j293 - m1 mbp
<marcan>
jannau: argh, sorry, just pushed it properly. I was really tired last night..
<marcan>
I also removed ARM from the depend of the config option
<sven>
huh, looks like SCO transfers just work but there's a ~2-3 second delay when I do parec | paplay
<sven>
i wonder if that's caused by not doing anything special for the SCO IPC
<marcan>
isn't that just normal latency for parec | paplay?
<marcan>
that sounds like a worst case setup for latency, to be honest
<marcan>
bluetooth, a dumb pipe, pulseaudio, ...
<sven>
no idea :D
<sven>
but yeah, maybe it's just the ghetto setup
off^ has joined #asahi-dev
pseigo has joined #asahi-dev
<marcan>
try actually going on a voice call or something (e.g. discord)
<sven>
hrm, that's gonna be annoying since this machine has no display or keyboard or mouse hooked up
<marcan>
heh
<marcan>
ssh -Y and run a browser remotely? :p
<sven>
lol, that might actually work :D
<maz>
Xpra has the option to route audio. never tried though...
<marcan>
there's also that actual loopback PA module which might be a saner option for this
<sven>
parec | pacat --latency-msec 1 sounds fine
<sven>
so i guess it just works \o/
<marcan>
nice!
<marcan>
maz: by the way, thoughts on the big.LITTLE kvm issue? I see people running into that recently... it kind of sucks to have to pin guests :(
<marcan>
I think macOS just fakes the ID registers to the guest and relies on the cores being *effectively* transparently compatible
<maz>
marcan: this is a QEMU issue.\
<marcan>
as in QEMU should pin guests by default?
<maz>
kvmtool doesn't care, for example.
<j`ey>
what's this?
<maz>
no, the issue is that QEMU starts a guest by sampling the id registers on one CPU, and tries to restore them on all of them.
<marcan>
oh, huh. really.
<maz>
if you have two types, it goes tits up.
<maz>
(effectively, a VM startup is implemented as a VM migration)
<marcan>
does KVM support faking/fixing ID registers so it can present a consistent view to the guest?
<maz>
no. we explicitely expose the underlying HW because we have so many bugs to mitigate in the guest...
<marcan>
right, so that would probably confuse guests if cores move around, so you'd still need pinning...
<maz>
I have a vague plan to allow the exposure of a virtual MIDR with a list of actual cores you can run on, and let the guest deal with that.
<maz>
but that's pretty low on my laudry list.
<marcan>
oh, like a set of MIDRs?
<maz>
it would also require some pretty heavy guest buy-in.
<marcan>
yeah, of course...
<marcan>
apple's game here is that they can get away with just pretending the cores are the same
<marcan>
in practice you can probably get away with pretending all cores are big, since any buglets are likely to happen there or in both, probably
<maz>
yup. we'd tell the guest: "this is a fake CPU, but here's the list of MIDRs you may see, go and enable all the errata that match this@.
<marcan>
(in apple's case)
<maz>
don't under-estimate the capacity of small core designers to fuck things up...
<marcan>
:)
<marcan>
I think Apple's small cores are mostly cut down big cores, but yeah
<marcan>
this hasn't hit anyone else because nobody else does real VMs on big.LITTLE?
<j`ey>
marcan: btw tested on m1 mba. wifi nvme battery rtc all work
<marcan>
\o/
<maz>
people do (we certainly do), but only QEMU has this behaviour, and Linux in general isn't too affected by the CPU migration under its feet... but it's mostly luck ATM.
<marcan>
right, sigh.
<maz>
anyway, -SIGLUNCH.
<marcan>
maybe we should cook up a qemu patch to make it at least not broken, and ship that, and see how it goes
millenialhacker has joined #asahi-dev
<sven>
does the M2 still have the 4378/4387 chips for wifi/bluetooth?
<marcan>
I think so, but -ENOPCIE
<marcan>
need to fix that
<marcan>
(just the fuse table probably)
<sven>
ah, true :D
<marcan>
might do that now, so I can just say wifi works for the progress report
<sven>
hrm, i guess i could also just update my mba and look into /usr/share/firmware or whatever
<marcan>
bbiab, dinner
<marcan>
that too :)
<marcan>
but yeah I think someone said it was 4387?
<marcan>
actually wait
<marcan>
ah, nevermind
<marcan>
wifi-chipset = 4378
<marcan>
sven: it's in the adt
<marcan>
so yeah
<marcan>
4378 it seems
<marcan>
no change
<sven>
ah, nice
<sven>
guess that just leaves the firmware renaming script for bluetooth
<marcan>
yup
<marcan>
eh, might do an M2 continuation bring-up stream in a bit, after dinner/shower. why the heck not.
millenialhacker has quit [Ping timeout: 480 seconds]
<sven>
\o/
<marcan>
SPMI should be simple (and might even get me writing a real driver or help with the old hardware, the old one is kind of bad)
<marcan>
then the PCIe fuse bits
<marcan>
and maybe even dockchannel HID if everything else goes fast
<marcan>
we'll see
<j`ey>
stream :o
pseigo has quit [Quit: left]
pseigo has joined #asahi-dev
<marcan>
after dinner :)
yuyichao has joined #asahi-dev
millenialhacker has joined #asahi-dev
off^ has quit [Ping timeout: 480 seconds]
tanty has joined #asahi-dev
millenialhacker has quit [Ping timeout: 480 seconds]
pseigo has quit [Ping timeout: 480 seconds]
off^ has joined #asahi-dev
kettenis has joined #asahi-dev
amarioguy has quit [Remote host closed the connection]
the_lanetly_052__ has quit [Ping timeout: 480 seconds]