In the past, AMDRadeonX6000 was mangled to use some of its code, primarily for the DCN display, and historically for the removed buggy VCN code. Since the first stable release, that has been replaced with a proper reimplementation, and in future commits further bug fixes to AMD's logic, which will also be used in the future AMD dGPU support.
AMDRadeonX6000Framebuffer is currently mangled because of the DCN display hardware once again. There are patches done to it to fix assumptions for RDNA dGPUs that crumbled when I used it for the Vega iGPUs.
For merging NootRX with NootedRed, and working towards removing the reliance on Lilu's DeviceInfo, new Runtime Meta Classes must be created inheriting from the appropriate classes within the aforementioned kext thus emplacing the correct logic but only for the iGPUs, which is additionally cleaner than the current approach as it is mere hacks.
In the past, AMDRadeonX6000 was mangled to use some of its code, primarily for the DCN display, and historically for the removed buggy VCN code. Since the first stable release, that has been replaced with a proper reimplementation, and in future commits further bug fixes to AMD's logic, which will also be used in the future AMD dGPU support.
AMDRadeonX6000Framebuffer is currently mangled because of the DCN display hardware once again. There are patches done to it to fix assumptions for RDNA dGPUs that crumbled when I used it for the Vega iGPUs.
For merging NootRX with NootedRed, and working towards removing the reliance on Lilu's DeviceInfo, new Runtime Meta Classes must be created inheriting from the appropriate classes within the aforementioned kext thus emplacing the correct logic but only for the iGPUs, which is additionally cleaner than the current approach as it is mere hacks.