OpenBSD Journal

Hardware Accelerated ATI/Nvidia Drivers

Contributed by jason on from the selling-our-souls-for-sweet-sweet-candy dept.

Fresh on the heels of work by Owain Ainsworth (oga@) and Matthieu Herrb (matthieu@) to build in DRI support for OpenBSD, they've imported the first batch of hardware accelerated drivers for Nvidia and ATI graphic chipsets.

List:       openbsd-cvs
Subject:    CVS: cvs.openbsd.org: src
From:       Owain Ainsworth 
Date:       2008-03-31 24:56:11
Message-ID: 200804010056.lB4LuB3r031337 () cvs ! openbsd ! org

CVSROOT:	/cvs
Module name:	src
Changes by:	oga@cvs.openbsd.org	2008/03/31 17:56:11

Modified files:
	sys/dev/dri    : nvblob.c atiblob.c blobpos.h

Log message:
Add support for hardware acceleration.  Tested with Quake3 and xeyes.
Enable hw.dri.compatibility.evil before loading kernel module.

From FreeBSD

ok matthieu@

While widespread compatibility is probably still months away, at least we have the potential for modern gaming in OpenBSD 4.4. Watch for more commits in this section of the tree and submit test reports for your chipset versions.

(Comments are closed)

Comments

  1. By Anonymous Coward (24.222.229.173) on

    This is exciting. Does this mean a FlightGear port is soon to be a possibility?

  2. By Anonymous Coward (84.197.60.39) on

    April Fool's. Hardy har har.

    Comments

    1. By Anonymous Coward (203.166.124.3) on

      i hate april fools

      Comments

      1. By Anonymous Coward (24.113.150.55) on

        > i hate april fools

        If only there were some way to punch people in the face over the internet when they do shit like this...

    2. By Mark Peloquin (incripshin) on

      The part about testing the driver with xeyes should have clued me in. It didn't.

      Comments

      1. By Troels Just (83.92.47.210) on http://www.troelsjust.dk

        > The part about testing the driver with xeyes should have clued me in. It didn't.

        Or these two lines:

        "Modified files:
        sys/dev/dri : nvblob.c atiblob.c blobpos.h"

        The word "blob" got me thinking that something was up! ;)

        Comments

        1. By Anonymous Coward (212.20.215.129) on

          > > The part about testing the driver with xeyes should have clued me in. It didn't.
          >
          > Or these two lines:
          >
          > "Modified files:
          > sys/dev/dri : nvblob.c atiblob.c blobpos.h"
          >
          > The word "blob" got me thinking that something was up! ;)

          "from the selling-our-souls-for-sweet-sweet-candy dept." was a pretty clear giveaway (once I spotted it ;-) ).

          Comments

          1. By Perfors (213.147.164.180) on

            > > > The part about testing the driver with xeyes should have clued me in. It didn't.
            > >
            > > Or these two lines:
            > >
            > > "Modified files:
            > > sys/dev/dri : nvblob.c atiblob.c blobpos.h"
            > >
            > > The word "blob" got me thinking that something was up! ;)
            >
            > "from the selling-our-souls-for-sweet-sweet-candy dept." was a pretty clear giveaway (once I spotted it ;-) ).
            >

            "Date: 2008-03-31 24:56:11"
            This is also very interesting (once you see it :))

            Comments

            1. By Anonymous Coward (212.20.215.129) on

              > > > > The part about testing the driver with xeyes should have clued me in. It didn't.
              > > >
              > > > Or these two lines:
              > > >
              > > > "Modified files:
              > > > sys/dev/dri : nvblob.c atiblob.c blobpos.h"
              > > >
              > > > The word "blob" got me thinking that something was up! ;)
              > >
              > > "from the selling-our-souls-for-sweet-sweet-candy dept." was
              > > a pretty clear giveaway (once I spotted it ;-) ).
              > >
              >
              > "Date: 2008-03-31 24:56:11"
              > This is also very interesting (once you see it :))

              Message-ID: 200804010056.lB4LuB3r031337 () ...

              ...31337 Coincidence? I think not. Let's rip this ID apart.

              Comments

              1. By jason (jason) jason@dixongroup.net on http://www.dixongroup.net/

                > Message-ID: 200804010056.lB4LuB3r031337 () ...
                >
                > ...31337 Coincidence? I think not. Let's rip this ID apart.

                Good catch. That's the only tidbit, the rest is original.

                -J.

                Comments

                1. By Anonymous Coward (66.207.218.19) on

                  > > Message-ID: 200804010056.lB4LuB3r031337 () ...
                  > >
                  > > ...31337 Coincidence? I think not. Let's rip this ID apart.
                  >
                  > Good catch. That's the only tidbit, the rest is original.
                  >
                  > -J.
                  >

                  so the uB3r is original?

                  Comments

                  1. By Anonymous Coward (134.76.113.61) on

                    > > > Message-ID: 200804010056.lB4LuB3r031337 () ...
                    > > >
                    > > > ...31337 Coincidence? I think not. Let's rip this ID apart.
                    > >
                    > > Good catch. That's the only tidbit, the rest is original.
                    > >
                    > > -J.
                    > >
                    >
                    > so the uB3r is original?

                    and what about balu be(a)r?

        2. By Anonymous Coward (87.230.108.21) on

          > > The part about testing the driver with xeyes should have clued me in. It didn't.
          >
          > Or these two lines:
          >
          > "Modified files:
          > sys/dev/dri : nvblob.c atiblob.c blobpos.h"
          >
          > The word "blob" got me thinking that something was up! ;)

          or the date:

          Date: 2008-03-31 24:56:11

    3. By TomazZ (193.77.154.191) on

      > April Fool's. Hardy har har.

      sys/dev/dri : nvblob.c atiblob.c blobpos.h

      Blob, blob, blob :D

  3. By Anonymous Coward (131.177.204.78) on

    Haha, nice one.

    btw, whats the real dri status?

    Comments

    1. By Anonymous Coward (92.228.29.26) on

      > Haha, nice one.
      >
      > btw, whats the real dri status?

      Haha. You must be new here. ;)

    2. By oga (87.194.220.76) oga@openbsd.org on

      > Haha, nice one.
      >
      > btw, whats the real dri status?

      Coming.

      src/sys/dev/pci/drm is there, but that's out of date.

      Comments

      1. By Anonymous Coward (213.168.66.183) on


        > src/sys/dev/pci/drm is there, but that's out of date.

        Give's me a "Hello, World!" :)

  4. By Alex Hafey (192.193.245.15) on

    What about a 3dfx driver :-P

  5. By Paladdin (213.97.233.52) on

    Talking about 'kernel module loading' feels so itchy in this, our context... Nice one! xD

  6. By Anonymous Coward (129.132.105.165) on

    Searching for all the hints that it is an April Fools joke is really fun. Lots of small details in the posting, still it tricked me for second. Well done!

  7. By Aapo Lehtinen (m90) aapo@pokat.org on

    I was also expecting WPA, Flash for lynx and integrated Java.. well, not a bad one. Happy april fools!

  8. By Anonymous Coward (91.121.102.64) on

    Sick that you made jokes about ATI 'course they even opned their Firmware. So if OpenBSD raly supports once dri and with ATI cards propably nobody gonna beliefs it at the first moment... :-)

  9. By Anonymous Coward (193.166.235.97) on

    Way to go. You're finally coming to the year 2000!

  10. By Anonymous Coward (69.207.171.114) on

    Let me know when I can play Duke Nukem Forever on OpenBSD.

    Comments

    1. By Brad (2001:470:8802:3:216:41ff:fe17:6933) brad at comstyle dot com on

      > Let me know when I can play Duke Nukem Forever on OpenBSD.

      Let me know when Duke Nukem Forever is ever released. Going on 12 years and nothing.

      Comments

      1. By Anonymous Coward (24.222.223.104) on

        > > Let me know when I can play Duke Nukem Forever on OpenBSD.
        >
        > Let me know when Duke Nukem Forever is ever released. Going on 12 years and nothing.

        They plan to debut it on the new Amiga...

        Comments

        1. By Miod Vallat (miod) on

          > They plan to debut it on the new Amiga...
          >

          Debut it, or debug it?

      2. By raw (84.135.107.219) on

        > > Let me know when I can play Duke Nukem Forever on OpenBSD.
        >
        > Let me know when Duke Nukem Forever is ever released. Going on 12 years and nothing.

        Wich is, coinicdally, the age of OpenBSD.

        Comments

        1. By Janne Johansson (jj) jj@inet6.se on .

          > > > Let me know when I can play Duke Nukem Forever on OpenBSD.
          > > Let me know when Duke Nukem Forever is ever released. Going on 12 years and nothing.
          >
          > Wich is, coinicdally, the age of OpenBSD.

          That is no coincidence, it is a conspiracy!

  11. By Anonymous Coward (62.103.255.235) on

    you fuckers..

  12. By Anonymous Coward (216.68.194.96) on

    Also, support for Zseries and 1TB ram, and 16TB disk supported now! Start making your raindown tables and whatnot now!

    Sure would be nice to be able to run OpenBSD on an expensive z10 mainframe...

Latest Articles

Credits

Copyright © - Daniel Hartmeier. All rights reserved. Articles and comments are copyright their respective authors, submission implies license to publish on this web site. Contents of the archive prior to as well as images and HTML templates were copied from the fabulous original deadly.org with Jose's and Jim's kind permission. This journal runs as CGI with httpd(8) on OpenBSD, the source code is BSD licensed. undeadly \Un*dead"ly\, a. Not subject to death; immortal. [Obs.]