Attachment 12528 Details for Bug 13233 – FreeBSD agp support files moved in __FreeBSD_version >= 800003

[patch] FreeBSD agp support files moved in __FreeBSD_version >= 800003

0001-freebsd-agp-support-files-moved-in-__FreeBSD_versio.patch (text/plain), 1.29 KB, created by Robert Noland on 2007-11-13 15:45:50 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Robert Noland

Created: 2007-11-13 15:45:50 UTC

Size: 1.29 KB

patch

obsolete

>From 49a0e864fee219ed6db4283125aa8eea47fbbb5c Mon Sep 17 00:00:00 2001
>From: Robert Noland <rnoland@squirrel.acs.internap.com>
>Date: Tue, 13 Nov 2007 18:41:12 -0500
>Subject: [PATCH] freebsd: agp support files moved in __FreeBSD_version >= 800003
>
>---
> bsd-core/drmP.h           |    4 ++++
> bsd-core/drm_agpsupport.c |    4 ++++
> 2 files changed, 8 insertions(+), 0 deletions(-)
>
>diff --git a/bsd-core/drmP.h b/bsd-core/drmP.h
>index c319beb..4351c34 100644
>--- a/bsd-core/drmP.h
>+++ b/bsd-core/drmP.h
>@@ -76,7 +76,11 @@ typedef struct drm_file drm_file_t;
> #if defined(__FreeBSD__)
> #include <sys/rman.h>
> #include <sys/memrange.h>
>+#if __FreeBSD_version >= 800003
>+#include <dev/agp/agpvar.h>
>+#else /* __FreeBSD_version >= 800003 */
> #include <pci/agpvar.h>
>+#endif /* __FreeBSD_version >= 800003 */
> #include <sys/agpio.h>
> #if __FreeBSD_version >= 500000
> #include <sys/mutex.h>
>diff --git a/bsd-core/drm_agpsupport.c b/bsd-core/drm_agpsupport.c
>index 6f963b9..e40d775 100644
>--- a/bsd-core/drm_agpsupport.c
>+++ b/bsd-core/drm_agpsupport.c
>@@ -36,7 +36,11 @@
> #include "drmP.h"
> 
> #ifdef __FreeBSD__
>+#if __FreeBSD_version >= 800003
>+#include <dev/agp/agpreg.h>
>+#else /* __FreeBSD_version >= 800003 */
> #include <pci/agpreg.h>
>+#endif /* __FreeBSD_version >= 800003 */
> #include <dev/pci/pcireg.h>
> #endif
> 
>-- 
>1.5.3.2
>

Actions: View | Splinter Review

Attachments on bug 13233: 12526 | 12527 | 12528 | 12529

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.