Re: Call for tests: DRM fixes for upcoming NetBSD 10.1

Hi Rin,

> On the other hand, we concern potential regressions caused by the
> pullup. It would really be appreciated if you can test 10.0_STABLE
> during **this weekend**.

Sorry for replying so late but hey, here's another "thumbs up!":

radeondrmkmsfb0 and X11 are still working fine with a fresh 10-STABLE
as of last weekend on a HP Proliant DL360-Gen 6 server.  This,
though, *not* woth the standard GENERIC kernel but with the following
one-word patch enabling radeon(4) for this system board.

					Martin Neitzel


    Enable radeon(4) for the ATI Technologies ES1000.
    
    NetBSD deals just fine with the ATI Technologies ES1000
    built into a HP Proliant DL360 Gen6 server.
    We became happy campers with wsdisplay0 attaching to
    radeondrmkmsfb0 attaching to radeon0.

diff --git a/sys/external/bsd/drm2/radeon/radeon_pci.c b/sys/external/bsd/drm2/radeon/radeon_pci.c
index fccf77afef34..7a05932dc6b5 100644
--- a/sys/external/bsd/drm2/radeon/radeon_pci.c
+++ b/sys/external/bsd/drm2/radeon/radeon_pci.c
@@ -133,7 +133,7 @@ extern const struct pci_device_id *const radeon_device_ids;
 extern const size_t radeon_n_device_ids;
 
 /* Set this to false if you want to match R100/R200 */
-bool radeon_pci_ignore_r100_r200 = true;
+bool radeon_pci_ignore_r100_r200 = false;
 
 static bool
 radeon_pci_lookup(const struct pci_attach_args *pa, unsigned long *flags)