Bug 17931 (xtraeme) - libpciaccess ported to NetBSD
Summary: libpciaccess ported to NetBSD
Status: RESOLVED FIXED
Alias: xtraeme
Product: xorg
Classification: Unclassified
Component: Lib/pciaccess (show other bugs)
Version: 7.4 (2008.09)
Hardware: Other NetBSD
: highest major
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-06 11:19 UTC by Juan RP
Modified: 2008-10-11 11:45 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Patches to build netbsd_pci.c and build/link correctly. (2.20 KB, patch)
2008-10-06 11:19 UTC, Juan RP
no flags Details | Splinter Review
NetBSD code for libpciaccess. (8.88 KB, text/plain)
2008-10-06 11:21 UTC, Juan RP
no flags Details

Description Juan RP 2008-10-06 11:19:49 UTC
Created attachment 19412 [details] [review]
Patches to build netbsd_pci.c and build/link correctly.

Hi,

I've ported libpciaccess to NetBSD. It's based in the OpenBSD code, but with
differences because on NetBSD, to set MTRRs we have to use i386/x86_64_set_mtrr()
and link to libi386 or libx86_64.

The patch has been tested successfully on latest NetBSD distribution as well as
latest xorg-server version (1.5.1).
Comment 1 Juan RP 2008-10-06 11:21:39 UTC
Created attachment 19413 [details]
NetBSD code for libpciaccess.
Comment 2 Julien Cristau 2008-10-11 11:45:53 UTC
On Mon, Oct  6, 2008 at 11:19:50 -0700, bugzilla-daemon@freedesktop.org wrote:

> I've ported libpciaccess to NetBSD.

applied, thanks.

commit 4c1c607c602e5e8d9277b9c01edfa7a8d10333cd
Author: Juan RP <xtraeme@gmail.com>
Date:   Sat Oct 11 20:28:03 2008 +0200

    Add NetBSD support
    
    It's based in the OpenBSD code, but with differences because on NetBSD,
    to set MTRRs we have to use i386/x86_64_set_mtrr() and link to libi386
    or libx86_64.
    
    X.Org bug#17931 <http://bugs.freedesktop.org/show_bug.cgi?id=17931>


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.