#asahi · 2023-03-25 10:29
marcaneh, framebuffer compression is more important than scaling for performance anyway :p#asahi · 2023-03-25 10:29
marcanthen we should do that at some point, yeah#asahi · 2023-03-25 10:29
marcanoh, I thought we had scaling hooked up#asahi · 2023-03-25 10:28
marcanI think in principle if say $game sets up a 1024x768 framebuffer and wants to present via DCP on Wayland it should be possible for the compositor to configure that surface as the primary plane if all the moving parts work right (not sure if they do)#asahi · 2023-03-25 10:27
marcanyes, and that is supported in the dcp driver, isn't it?#asahi · 2023-03-25 10:26
marcanit's just two ways of doing the same thing, one legacy. we're not doing legacy.#asahi · 2023-03-25 10:25
marcanlike literally on Intel you can xrandr switch to an 800x600 mode on a 1080p laptop screen, or xrandr create a virtual 800x600 screen and scale it to 1080p with a 1080p mode selected, and they are the *same thing* as far as I know, at the hardware.#asahi · 2023-03-25 10:24
marcanremember x86 is a pile of legacy upon legacy upon legacy in all dimensions, and our job here is to not be burdened by that kind of stuff and do things right#asahi · 2023-03-25 10:23
marcanbut it no longer is the driver's job to pretend a screen that only has one mode can do more modes like other laptops do#asahi · 2023-03-25 10:23
marcanso if you really want to render your UI at a lower resolution and scale it, in principle nothing stops wayland compositors from offering that option#asahi · 2023-03-25 10:23
marcanapproximately zero laptop panels support changing the resolution, intel/AMD/nvidia drivers just emulate it with internal scaling. there's no reason to emulate that in the driver any more since compositors can configure scaling like that themselves if they really want to.#asahi · 2023-03-25 10:20
marcanbut it makes no sense for UIs#asahi · 2023-03-25 10:20
marcanyes, which is why games *do* usually let you render at a lower resolution than the display, and that all works perfectly fine on wayland#asahi · 2023-03-25 10:19
marcanthey do now, so that's obsolete#asahi · 2023-03-25 10:19
marcanthe only reason we had it is OSes not supporting UI scaling properly#asahi · 2023-03-25 10:19
marcanthat's a legacy concept inherited from CRTs#asahi · 2023-03-25 10:18
marcanchanging the resolution on LCD panels hasn't made sense since LCD panels were invented#asahi · 2023-03-25 10:17
marcanif you want to make things larger/smaller, change the display scale#asahi · 2023-03-25 10:17
marcanchanging the resolution is supported on desktops/external monitors. changing the resolution of the internal panel is not supported nor does it make any sense.#asahi · 2023-03-25 10:16
marcanI think that one is already reported on the github issue#asahi · 2023-03-25 10:15
marcanah-: that's not a GPU crash, that's a GPU fault. mesa bug or firefox bug.#asahi · 2023-03-25 10:14
marcanyes.#asahi · 2023-03-25 09:55
marcan(and power management, but everyone does that in firmware)#asahi · 2023-03-25 09:55
marcanthe firmware on apple GPUs just handles scheduling and submission and preemption etc, not the actual rendering#asahi · 2023-03-25 09:55
marcan(I know because I reverse engineered F32 way back :p)#asahi · 2023-03-25 09:54
marcanAMD has a pile of little blobs running the actual 3D command pipeline on their custom F32 cores, on Apple that's all hardware.#asahi · 2023-03-25 09:54
marcanj`ey_: actually come to think of it, there is *less* firmware on apple than on AMD, as far as what the firmware actually does#asahi · 2023-03-25 09:51
marcan(apple didn't even try though, their GL runs geometry shaders on the CPU as far as I know)#asahi · 2023-03-25 09:51
marcanevidently you *can* emulate geometry shaders and TF, there's just many ways of doing it and your options are better when you're talking directly to hardware#asahi · 2023-03-25 09:50
marcanyes, I saw that#asahi · 2023-03-25 09:49
marcan-y#asahi · 2023-03-25 09:49
marcanthe meme is just because people make stuff up about apple stuff, along the same lines as "m1s are amazingly only because macos is so optimized for them"#asahi · 2023-03-25 09:49
marcanif it were a "metal gpu" it would have mesh shaders, which it doesn't#asahi · 2023-03-25 09:48
marcanj`ey_: it definitely talks to hardware, all the command streams are processed by hardware#asahi · 2023-03-25 09:47
marcanthere's this pervasive myth that Apple GPUs are "Metal GPUs" or something, which is completely wrong#asahi · 2023-03-25 09:44
marcannsklaus: I think you mean lina?#asahi · 2023-03-25 09:41
marcanthat was always the plan, yes#asahi · 2023-03-25 09:40
marcan(thank alyssa for that :p)#asahi · 2023-03-25 09:40
marcantransform feedback is already implemented in dev trees, other stuff will come in due time#asahi · 2023-03-25 09:39
marcan(other than my own)#asahi · 2023-03-25 09:39
marcanthe speaker stuff will not be made available to anyone who isn't building their own kernels until it is fully tested and validated on all platforms we intend to enable it on. this is a safety thing and I will *not* be blowing up anyone's speakers.#asahi · 2023-03-25 09:38
marcanit's not ready yet#asahi · 2023-03-23 17:13
marcanbut even if they were implemented in SMC firmware, SMC has no nonvolatile memory other than the BMIC itself#asahi · 2023-03-23 17:12
marcanthe charge thresholds aren't even implemented in hardware, they're implemented in software#asahi · 2023-03-23 17:12
marcanthere can't be any persistence because there is no nonvolatile memory involved, this is by design#asahi · 2023-03-23 17:12
marcanbut that never got merged/done#asahi · 2023-03-23 17:11
marcanthe real answer here is that upower should be doing this#asahi · 2023-03-23 17:11
marcanmkurz: there is no persistence, this is the OS's job#asahi · 2023-03-23 17:10
marcanI don't think we touched nvme since then?#asahi · 2023-03-23 17:09
marcantpw_rules: it wasn't a year ago, it was november