Skip to content

Latest commit

 

History

History
48 lines (38 loc) · 2.42 KB

File metadata and controls

48 lines (38 loc) · 2.42 KB

RDNA2 and RDNA3 Experimental Support

Scope

NootedRed is primarily an AMD Vega iGPU compatibility kext. This repository does not implement native RDNA2 or RDNA3 bring-up yet.

This document describes the current experimental compatibility path that lets selected RDNA2 and RDNA3 iGPUs run through the existing Renoir and GreenSardine pipeline.

Current model

  • Native and validated path: Raven, Picasso, Renoir, GreenSardine.
  • Experimental compatibility path: selected RDNA2 and RDNA3 iGPUs are mapped onto the GreenSardine profile.
  • Generic experimental fallback: unknown AMD iGPUs can be forced onto the same profile through a boot argument.

Experimental RDNA mappings

The following device IDs are recognized as experimental mappings:

  • RDNA3: 0x15BF
  • RDNA2: 0x1681, 0x1682, 0x1686

These IDs are intentionally routed to the GreenSardine compatible initialization profile to reduce hard failures and enable testing.

Boot arguments

  • NRedAllowUnsupportedIGPU=1
    • Enables a soft fallback for unknown AMD iGPU device IDs.
    • Without this option, unknown IDs still trigger a panic to preserve safe default behavior.

What the fallback does

  • Uses Renoir and GreenSardine capability path and enum revision defaults.
  • Keeps existing HWLibs, X5000, X6000FB, and AppleGFXHDA patch flow intact.
  • Expands HDMI audio wrapper matching for AMD devices while running a Renoir-derived profile.
  • Extends injected IOPCIMatch lists for accelerator, framebuffer, and HWServices to include experimental RDNA2 and RDNA3 IDs.

Limitations

  • This is not native RDNA2 or RDNA3 support.
  • Device-specific IP blocks, firmware, power management tuning, and display controller differences are not fully implemented.
  • Stability and feature completeness vary by platform and macOS version.
  • Desktop dGPU coverage is not complete in this patch set. The current focus is AMD APU iGPU compatibility paths.

Recommended validation checklist

  • Boot with and without external display.
  • Verify framebuffer init, acceleration, and sleep and wake behavior.
  • Verify HDMI and DP audio routing.
  • Check logs for profile selection and fallback notices.
  • Run stress tests for sustained graphics workloads.

Developer notes

If you add new RDNA IDs:

  1. Add them to the profile table in NRed processPatcher logic.
  2. Keep them on experimental profile until validated.
  3. Promote to native profile only after dedicated register, firmware, and power path support is implemented.