Lloyd Parkes writes:
> On Sat, 2025-02-15 at 12:47 +1100, matthew green wrote:
> > > On the bright side (for me anyway), I found that the AMDGPU code
> > > wasn't
> > > working for me because the support for cards as old as mine is
> > > optional. I had to set the config option "AMDGPU_CIK" to enable
> > > support
> > > for my R9 290.
> >
> > this is odd. i believe your card is pciid 0x699F? that should be
> > matching eg:
> >
>
> My card's PCIID is 0x67b1 and it gets identified as "Hawaii PRO". I
> have no idea what card is 0x699F because the AMD product line at that
> time was completely chaotic.
OK, that's odd. does the radeon driver not work here? from
sys/external/bsd/drm2/dist/include/drm/drm_pciids.h:
4:#define radeon_PCI_IDS \
5: {0x1002, 0x1304, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
CHIP_KAVERI|RADEON_IS_MOBILITY|RADEON_NEW_MEMMAP|RADEON_IS_IGP}, \
...
281: {0x1002, 0x67B1, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
CHIP_HAWAII|RADEON_NEW_MEMMAP}, \
which should make it attach as a radeon? libdrm and Mesa
also seem to want to radeon-ify it?
external/mit/libdrm/dist/radeon/r600_pci_ids.h:483:CHIPSET(0x67B1, HAWAII_67B1,
HAWAII)
external/mit/MesaLib/dist/include/pci_ids/radeonsi_pci_ids.h:155:CHIPSET(0x67B1,
HAWAII)
(radeonsi i think works with both radeon and amdgpu drm.)
i wonder what is happening here.
.mrg.
