#
#asahi-dev · 2026-09-24 12:36
chadmedthese were all decisions that have to have been made ~3 years ago before everything became expensive and on fire and evil
#asahi-dev · 2026-09-24 12:35
chadmedi feel like theyll converge again
#asahi-dev · 2026-09-24 12:34
nickchanto the point m6/a20 cores are materially different from each other
#asahi-dev · 2026-09-24 12:33
chadmedor even just M4 Series Feature Support (incl. A18 Pro)
#asahi-dev · 2026-09-24 12:33
myriaFair enough, pushing the extra stuff now
#asahi-dev · 2026-09-24 12:33
chadmedA18 & M4 Series Feature Support or something like that
#asahi-dev · 2026-09-24 12:33
nickchana-series and m-series relations are a mess since the A16/A17/M3
#asahi-dev · 2026-09-24 12:33
chadmed^
#asahi-dev · 2026-09-24 12:33
chaos_princessthrow it in together, a18 does not deserve a page of it's own :P
#asahi-dev · 2026-09-24 12:32
myriaBut question I had, do we want a separate page for the A18, or just lump it in with M4?
#asahi-dev · 2026-09-24 12:31
myriaHey, I'm adding some extra supported information to the website (see https://github.com/AsahiLinux/docs/pull/278)
#asahi-dev · 2026-09-24 12:30
svenlol :D
#asahi-dev · 2026-09-24 12:29
ndufresneFun fact, I remember working on the display controller of the OpenMoko Freerunner, and one bug requires to place the phone in the freezer for 30min or so and resume from suspend at low temprature to reproduce
#asahi-dev · 2026-09-24 12:29
chadmedthis is pretty much the only (major) issue ive encountered and like i said it was just because i was doing stuff we would never ship anyway
#asahi-dev · 2026-09-24 12:28
ndufresneIf there is anything in Weston that is incompatible with asahi gpu driver, file an issue, I'm sure we can fix it, but I'm not saying its good for desktop, use kde/mutter/wlroot based stuff, but its been better for testing overlay/underlay at low level then kmssink
#asahi-dev · 2026-09-24 12:28
chadmedsaying that it will crash if a strong breeze is blowing or the planets are orbiting a certain way is saying that it's extremely flakey and unreliable and fussy
#asahi-dev · 2026-09-24 12:27
chadmedlmao sorry im being cheeky, im saying that dcp is extremely temperamental and will crash if something is even slightly outside of what it expects
#asahi-dev · 2026-09-24 12:27
ndufresnechadmed ok, Canadian loves talking about weather, but you lost me about breeze and mercury here !
#asahi-dev · 2026-09-24 12:24
chadmedweston wont put a cursor on an overlay plane so you need to explicitly expose the plane as a cursor plane (which we dont do in production)
#asahi-dev · 2026-09-24 12:24
chadmedno i havent opened an issue for it because its a silly edge case
#asahi-dev · 2026-09-24 12:23
linkmauveDid you open an issue for that?
#asahi-dev · 2026-09-24 12:23
nickchanmerely from being able to use the hardware mmu via shadow paging in a virtual machine could improve performance
#asahi-dev · 2026-09-24 12:23
linkmauvechadmed, Weston doesn’t work correctly on Asahi?
#asahi-dev · 2026-09-24 12:23
chadmedkwin at least will immediately fall back to software compositing if it tries to do something dcp wouldnt like (e.g. putting a cursor too close to the edge of the screen lmao this display controller suuucks)
#asahi-dev · 2026-09-24 12:23
nickchanthe software MMU emulation is the perf killer of epic proportions
#asahi-dev · 2026-09-24 12:23
chadmedndufresne: Weston is not suitable for us as it does not gracefully handle us rejecting swaps when the breeze is blowing or mercury is in retrograde
#asahi-dev · 2026-09-24 12:22
nickchanfull system emulation is interesting because even without TSO
#asahi-dev · 2026-09-24 12:22
originaldave_mine is LLE/system emulation focused, compared to FEX which is HLE. they’re great folks though, and I’m looking at an interesting hyrid LLE-HLE method for the best of both worlds
#asahi-dev · 2026-09-24 12:19
chaos_princessoriginaldave_: use muvm.
#asahi-dev · 2026-09-24 12:18
linkmauveHow does your emulator compare to FEX btw?
#asahi-dev · 2026-09-24 12:18
linkmauveoriginaldave_, perhaps have a look at how FEX does it, alongside muvm?
#asahi-dev · 2026-09-24 12:15
originaldave_I ask because I was about to totally drop all the slow 16k page support stuff, but realized I might need it on Asahi
#asahi-dev · 2026-09-24 12:14
mango-602cf7Hey. x86-32 emulator author here. I couldn’t get a clear answer out of Google. Is there a per-process, or hypervisor, or any way to get 4k pages on Asahi? I’ve got an EL1 hypervisor going on my MacOS version
#asahi-dev · 2026-09-24 11:49
ndufresneIt would be nice to keep kms bit in shape, but it needs work, and needs HW specific allocation support
#asahi-dev · 2026-09-24 11:48
ndufresneRight, for testing on Wayland I aim for Weston, which has less magic, more config, but I won't hide that I work with bunch of Weston devs to help me
#asahi-dev · 2026-09-24 11:40
chadmedkwin for example still has issues with direct scanout on machines where the gpu and display controller are not the same thing, as it treats this as a multi-gpu setup
#asahi-dev · 2026-09-24 11:39
chadmedit is still useful for testing stuff like this without the interference of a wayland compositor doing unexpected things
#asahi-dev · 2026-09-24 11:35
sofusi also only learned about it for testing this specifik feature. I wish i can get it to run on wayland
#asahi-dev · 2026-09-24 11:30
ndufresneRight, kmssink is on its decay, I don't use it anymore myself, I always go for Wayland (Weston for niche use case, mutter/KDE for desktop work)
#asahi-dev · 2026-09-24 11:29
sofusbut anyway, my main goal was just testing everything works
#asahi-dev · 2026-09-24 11:28
sofusndufresne: i saw the HW specifik calculations but im not sure they make a difference when using the kmssink
#asahi-dev · 2026-09-24 11:21
chadmedbut we need to negotiate the correct pixel format and drm format modifier to make both the codec and display controller work properly so we cant rely on create_dumb and kludging things in the kms driver
#asahi-dev · 2026-09-24 11:20
chadmedthe tricky thing is that interchange/agx are similar to afbc in this regard. software is supposed to treat them as opaque/single-plane formats but the interface to the display controller requires the compression buffer metadata to be programmed in by us
#asahi-dev · 2026-09-24 11:18
ndufresneLet's say, we got away for now with AFBC since it's a single plane, we need to do more work, rmader was on that recently
#asahi-dev · 2026-09-24 11:16
ndufresneBut we can code HW specific offset calculations in gst v4l plugin, it's much more productive then wait for v4l3
#asahi-dev · 2026-09-24 11:14
ndufresnesofus: I'm missing some context, but it seems unlikely, specially for when opaque DRM formats are negotiated. But perhaps you mean we don't interpolate offset and second stride, I know there is still few gaps to fill there when drivers uses single allocation (which in v4l is forces to use the single plane interface, the API is really bad)
#asahi-dev · 2026-09-24 10:32
jannauprobably in dri-devel
#asahi-dev · 2026-09-24 10:32
jannauI think there were recently discussions to use custom create buffer IOCTLs for kms only devices to support video / compressed buffers
#asahi-dev · 2026-09-24 10:26
leioMaybe ndufresne has some thought about the above when he wakes up
#asahi-dev · 2026-09-24 10:18
sofuslol yeah 'KMS dumb buffers are not suitable for hardware-accelerated rendering nor video decoding'

plus ›