> On Dec 6, 2019, at 4:04 AM, Gerd Hoffmann <kraxel@xxxxxxxxxx> wrote:
>
>> Several MGA G200 SE machines don't respect the value of the startadd
>> register field. After more feedback on affected machines, neither PCI
>> subvendor ID nor the internal ID seem to hint towards the bug. All
>> affected machines have a PCI ID of 0x0522 (i.e., G200 SE A). It was
>> decided to flag all G200 SE A machines as broken.
>
>> - { PCI_VENDOR_ID_MATROX, 0x522, PCI_VENDOR_ID_SUN, 0x4852, 0, 0,
>> + { PCI_VENDOR_ID_MATROX, 0x522, PCI_ANY_ID, PCI_ANY_ID, 0, 0,
>> G200_SE_A | MGAG200_FLAG_HW_BUG_NO_STARTADD},
>> - { PCI_VENDOR_ID_MATROX, 0x522, PCI_ANY_ID, PCI_ANY_ID, 0, 0, G200_SE_A },
>
> Acked-by: Gerd Hoffmann <kraxel@xxxxxxxxxx>
Tested-by: John Donnelly <John.p.donnelly@xxxxxxxxxx>
This series of commits appear to resolve the display issue in 5.4.-rc8 as reported in :
https://gitlab.freedesktop.org/drm/misc/issues/7
52ca22daadbb 2019-12-06 | drm/mgag200: Flag all G200 SE A machines as broken wrt <startadd>
e0f1a41a45b3 2019-12-06 | drm/mgag200: Add workaround for HW that does not support 'startadd'
11a219a38f2d 2019-12-06 | drm/mgag200: Store flags from PCI driver data in device structure
a23512ace008 2019-12-06 | drm/mgag200: Extract device type from flags
There is one commit I did not apply :
[PATCH v2] drm/mgag200: Add module parameter to pin all buffers at offset 0
I don’t see a need for that now since we using the PCI-ID of 0x522 for the fix.
>
> cheers,
> Gerd
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@xxxxxxxxxxxxxxxxxxxxx
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.freedesktop.org_mailman_listinfo_dri-2Ddevel&d=DwIGaQ&c=RoP1YumCXCgaWHvlZYR8PZh8Bv7qIrMUB65eapI_JnE&r=t2fPg9D87F7D8jm0_3CG9yoiIKdRg4qc_thBw4bzMhc&m=cFYmB62lgH3WoOWZuvgMKjsgMXQUscmrypDlQhYpF_E&s=21ZEZohFZBQsEr5bo3sS4pMpCf2ca5KXFJq5X3XUzQw&e=
