-The latest drm code from FreeBSD 9.x current has been successfully ported to DragonFly BSD, [patch](http://leaf.dragonflybsd.org/~davshao/r600fbsd.diff) and git branch **r600fbsd** git://leaf.dragonflybsd.org/~davshao/dragonfly.git, and tested with a Radeon HD 4550 on an x86_64 machine (Shuttle SG45H7). However it must be remembered that testing has only been done with this one graphics card and it is completely unknown whether say an Intel machine will lock up solid. Also nothing was done to port the extensive Via drivers FreeBSD has already ported.

+Student: David Shao

+

+Mentor: Matthew Dillon

-## Introduction or what the heck is being talked about

+## Introduction

-We are talking about modern graphics card drivers that have already or are in the process of being written for Linux. Fortunately for the BSDs the source code that is the basis of these drivers, part hosted in git repositories accessible from [freedesktop.org](http://cgit.freedesktop.org/), and even the part that is now residing in the Linux kernel, is mostly licensed under terms compatible with the [MIT X License](http://www.opensource.org/licenses/mit-license.php), and therefore can be directly ported to DragonFly.

+We port to the BSDs modern graphics card drivers that have already or are in the process of being written for Linux. Fortunately for the BSDs the source code that is the basis of these drivers, userland hosted in git repositories accessible from [freedesktop.org](http://cgit.freedesktop.org/), and even the part that is now residing in the Linux kernel, is mostly licensed under terms compatible with the [MIT X License](http://www.opensource.org/licenses/mit-license.php), and therefore can be directly ported to the BSDs

+without licensing issues.

When we refer to DRM, we are referring to the [Direct Render Manager](http://dri.freedesktop.org/wiki/DRM) that is a kernel module arbitrating requests for various graphics related services. Because of this acronym, the source code for DragonFly's DRM module can be found in directory **sys/dev/drm**, while the source code for Linux'd DRM module has been split into **include/drm** hosting common header files and **drivers/gpu/drm**. Furthermore the Linux files have had vendor specific code split off into their own separate directories, a change the BSDs should consider since having all files in one directory is becoming rather unwieldy.

-## Previous work makes the port possible

+We feel the fastest path to porting is through the DragonFly BSD project, but we intend for our code to be the basis for

+ports to all the BSDs.

+

+## Acknowledgment to the FreeBSD Project

+

+We must acknowledge the hard work that previous porters of DRM such as Robert Noland of the FreeBSD project have already

+accomplished in translating much of earlier DRM to BSD kernel semantics. Simply take a diff of the FreeBSD and DragonFlyBSD

+versions of DRM and one can readily see that the hard work of translating the semantics of the locking for the Linux drivers

+has mostly been done, and better still can be done almost automatically. Furthermore the FreeBSD port has translated calls

+to manipulating hardware devices such as for AGP.

+

+## Goal

+

+We intend to write a portability layer that will allow the BSDs to use as much of the Linux drm code as possible.

+The developers of X.org / freedesktop.org related graphics drivers have their current efforts focused on Linux

+because they have to get something working anywhere as fast as possible. It is the BSDs responsibility to keep

+up with these efforts and to contribute back to these developers to justify the developers continuing

+to generously license their drm code under terms compatible with those of the BSD licenses.

+

+It is especially vital for Linux drm GEM, TTM, KMS code to be ported immediately to the BSDs because developers

+are in the process of removing userland modesetting code from current graphics drivers. To paraphrase what

+we have been told by freedesktop.org developers, if we do not port this code, very shortly the BSDs will be

+left only using the simplest VESA driver at 1024 x 768 resolution with no hardware acceleration.

+

+We believe that limiting divergence from Linux's drm code is the clearest path for the BSDs to be able

+to follow the latest drm developments.

+

+## Disclaimer

-Simply take a diff of the FreeBSD and DragonFlyBSD versions of DRM and one can readily see that the hard work of translating the semantics of the locking for the Linux drivers has mostly been done, and better still can be done almost automatically. The FreeBSD port represents the limits of what can be ported having worked out exclusive access mechanisms, but not having completely worked out equivalents of other Linux APIs such as **idr**, small integer ID management.

+Code that is uploaded to the experimental git branches has been verified to work for at most

+to use software based on X.org. In particular nothing is known about systems with graphics

+hardware from other vendors such as Intel or Nvidia.

-## What has been done and should be done

+We have experienced from ill-fated experiments forced rebooting with corruption of a ufs2 root filesystem;

+therefore, the same could well happen to you. Only use this code on a system with no valuable or

+irreplaceable data. We disclaim any warranty or fitness of code.

-The software used for graphics whether the kernel or Mesa is surprisingly resilient. As long as it compiles it will try and find a way with dealing with other mismatched components by falling back on default behavior. Working on a fast x86_64 machine, it is easy to be lulled into a false sense that things are working properly unless one checks the logs.

-Here the proper kernel module appears to be loaded. I wasted quite a bit of time earlier this week not realizing an error that led to the kernel module not being loaded at all that appeared from the messages to be a device non-existence problem.

+We develop on the x86_64 machine then push our changes to the git experimental branch

+**gsocdrmalpha** at

+

+git://leaf.dragonflybsd.org/~davshao/dragonfly.git

+

+We then pull the changes to the i386 machine to test build and compatibility.

+

+

+### Sample **dmesg* output

+

+The software used for graphics whether the kernel or userland Mesa is surprisingly resilient. As long as it compiles it will try and find a way with dealing with other mismatched components by falling back on default behavior. Working on a fast x86_64 machine, it is easy to be lulled into a false sense that things are working properly unless one checks the logs.

+

+Here the proper kernel module appears to be loaded for the x86_64 machine. We have on previous occasions not realized an error that led to the kernel module not being loaded at all that appeared from the messages to be a device non-existence problem.

drm0: <ATI Radeon HD 4550> on vgapci0

vgapci0: child drm0 requested pci_enable_busmaster

@@ -30,11+80,21 @@ Here the proper kernel module appears to be loaded. I wasted quite a bit of tim

info: [drm] Resetting GPU

info: [drm] writeback test succeeded in 1 usecs

+Similarly for the Radeon 9200-compatible i386 machine:

+

+ drm0: <ATI Radeon If RV250 9000> on vgapci0

+ vgapci0: child drm0 requested pci_enable_busmaster

+ info::[drm] AGP at 0xf8000000 64MB

+ info::[drm] Initialized radeon 1.31.0 20080613

+ info::[drm] Setting GART location based on new memory map

+ info::[drm] Loading R200 Microcode

+ info::[drm] writeback test succeeded in 1 usecs

+

### **var/log/Xorg.0.log** output

Somewhere on one's system are the logs of the latest startup of the X server and the modules it finds. There can be an alternate place if one installs a second X.org, say at */opt/xtest*, in which case instead of **/var/log/Xorg.0.log** one will look in **/opt/xtest/var/log/Xorg.0.log**.

-Here's a case of a failure where things are fine: I am composing this wiki from within Firefox 3.6.3 on a system where the proper module fails to load and yet where because of the machine's speed there is no discernible problem.

+Here's a case of a failure on the fast x86_64 machine where things appeared to be fine: we were composing this wiki from within Firefox 3.6.3 on a system where the proper module failed to load and yet where because of the machine's speed there was no discernible problem for this application.

drmOpenDevice: node name is /dev/dri/card0

drmOpenDevice: open result is 10, (OK)

@@ -47,9+107,9 @@ Here's a case of a failure where things are fine: I am composing this wiki from

(EE) AIGLX: reverting to software rendering

(II) AIGLX: Loaded and initialized /usr/pkg/lib/dri/swrast_dri.so

-The Mesa 7.4.x series simply didn't *have* an r600_drv.so driver so of course it can't be found. Mesa happily falls back to using software rendering and nothing seems greatly wrong.

+The Mesa 7.4.x series simply does not *have* a r600_drv.so driver so of course it can't be found. Mesa happily falls back to using software rendering and nothing seems greatly wrong.

-Now here is an example using latest Mesa and everything else from git where the driver is found:

+Now here is an example using latest Mesa and everything else from git on the x86_64 machine where the driver is found on the x86_64 machine:

[ 95.404] drmOpenDevice: node name is /dev/dri/card0

[ 95.405] drmOpenDevice: open result is 11, (OK)

@@ -65,369+125,72 @@ Now here is an example using latest Mesa and everything else from git where the

[ 95.507] (II) GLX: Initialized DRI GL provider for screen 0

[ 95.508] (II) RADEON(0): Setting screen physical size to 508 x 285

-Ironically I knew I was on the right track porting the latest git versions of the X.org stack when I succeeded in locking up hard my machine. That meant a real hardware acceleration module was being loaded by that the previous kernel could not handle it, which was why the latest drm from FreeBSD had to be imported for Radeon r600.

+Pkgsrc on the i386 r200 machine does have a supporting driver; therefore, we obtain from its log:

-## Installing from pkgsrc

-

-### GNU m4 1.4.14 and bison 2.4.2

-

-Patch both *devel/m4* and *devel/bison* using the patch idea from:

-<http://www.netbsd.org/cgi-bin/query-pr-single.pl?number=43098>

-

-Unfortunately the problems are in the *work* directories so that one needs the knowledge from

-<http://www.netbsd.org/docs/pkgsrc/components.html>

-to even get the patches to be applied.

-

-Install *pkgtools/pkgdiff*.

+ drmOpenDevice: node name is /dev/dri/card0

+ drmOpenDevice: open result is 10, (OK)

+ drmOpenByBusid: Searching for BusID pci:0000:01:00.0

+ drmOpenDevice: node name is /dev/dri/card0

+ drmOpenDevice: open result is 10, (OK)

+ drmOpenByBusid: drmOpenMinor returns 10

+ drmOpenByBusid: drmGetBusid reports pci:0000:01:00.0

+ (II) AIGLX: enabled GLX_MESA_copy_sub_buffer

+ (II) AIGLX: enabled GLX_SGI_make_current_read

+ (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control

+ (II) AIGLX: enabled GLX_texture_from_pixmap with driver support

+ (II) AIGLX: Loaded and initialized /usr/pkg/lib/dri/r200_dri.so

+ (II) GLX: Initialized DRI GL provider for screen 0

+ (II) RADEON(0): Setting screen physical size to 510 x 290

-### gstreamer 0.10

+Ironically we knew we were on the right track porting the latest git versions of the X.org stack when we succeeded in locking up hard our machine. That meant a real hardware acceleration module was being loaded that the previous kernel could not handle, which was why the latest drm from FreeBSD had to be imported.

-As of 2010-05-09, I find it necessary on x86_64 to use the following patch for

-pkgsrc gstreamer0.10, an eventual dependency of the full xfce desktop:

- [m4_fatal([Failed to get the Mesa version from `make -f bin/version.mk version`])])

+## Status

-#### C99 fpclassify()

+The latest drm code from FreeBSD 9.x current has been successfully ported to DragonFly BSD, [patch](http://leaf.dragonflybsd.org/~davshao/r600fbsd.diff) and git branch **r600fbsd** git://leaf.dragonflybsd.org/~davshao/dragonfly.git, and tested with a Radeon HD 4550 on an x86_64 machine (Shuttle SG45H7). However it must be remembered that testing has only been done with this one graphics card and it is completely unknown whether say an Intel machine will lock up solid. Also nothing was done to port the extensive Via drivers FreeBSD has already ported.