Attachment 27248 Details for Bug 18122 – possible patch

[patch] possible patch

xf86-video-chips.diff (text/plain), 1.46 KB, created by Matthieu Herrb on 2009-06-29 23:54:21 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Matthieu Herrb

Created: 2009-06-29 23:54:21 UTC

Size: 1.46 KB

patch

obsolete

>? log
>Index: src/ct_driver.c
>===================================================================
>RCS file: /cvs/xenocara/driver/xf86-video-chips/src/ct_driver.c,v
>retrieving revision 1.3
>diff -u -r1.3 ct_driver.c
>--- src/ct_driver.c	7 Mar 2009 11:22:09 -0000	1.3
>+++ src/ct_driver.c	30 Jun 2009 06:46:07 -0000
>@@ -480,14 +480,14 @@
>   { PCI_VENDOR_CHIPSTECH, (d), PCI_MATCH_ANY, PCI_MATCH_ANY, 0, 0, (i) }
> 
> static const struct pci_id_match chips_device_match[] = {
>-  CHIPS_DEVICE_MATCH(PCI_CHIP_65545, 0),
>-  CHIPS_DEVICE_MATCH(PCI_CHIP_65548, 0),
>-  CHIPS_DEVICE_MATCH(PCI_CHIP_65550, 0),
>-  CHIPS_DEVICE_MATCH(PCI_CHIP_65554, 0),
>-  CHIPS_DEVICE_MATCH(PCI_CHIP_65555, 0),
>-  CHIPS_DEVICE_MATCH(PCI_CHIP_68554, 0),
>-  CHIPS_DEVICE_MATCH(PCI_CHIP_69000, 0),
>-  CHIPS_DEVICE_MATCH(PCI_CHIP_69030, 0),
>+  CHIPS_DEVICE_MATCH(PCI_CHIP_65545, CHIPS_CT65545),
>+  CHIPS_DEVICE_MATCH(PCI_CHIP_65548, CHIPS_CT65548),
>+  CHIPS_DEVICE_MATCH(PCI_CHIP_65550, CHIPS_CT65550),
>+  CHIPS_DEVICE_MATCH(PCI_CHIP_65554, CHIPS_CT65554),
>+  CHIPS_DEVICE_MATCH(PCI_CHIP_65555, CHIPS_CT65555),
>+  CHIPS_DEVICE_MATCH(PCI_CHIP_68554, CHIPS_CT68554),
>+  CHIPS_DEVICE_MATCH(PCI_CHIP_69000, CHIPS_CT69000),
>+  CHIPS_DEVICE_MATCH(PCI_CHIP_69030, CHIPS_CT69030),
>   { 0, 0, 0 },
> };
> #endif
>@@ -813,7 +813,7 @@
> 
>     if (!setupDone) {
> 	setupDone = TRUE;
>-        xf86AddDriver(&CHIPS, module, 0);
>+        xf86AddDriver(&CHIPS, module, HaveDriverFuncs);
> 
> 	/*
> 	 * Modules that this driver always requires can be loaded here

Actions: View | Splinter Review

Attachments on bug 18122: 19744 | 19745 | 19746 | 25333 | 27248 | 27396

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.