Announcement

Collapse
No announcement yet.

Raspberry Pi Can Now Run Quake 3 On Open Graphics

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Raspberry Pi Can Now Run Quake 3 On Open Graphics

    Phoronix: Raspberry Pi Can Now Run Quake 3 On Open Graphics

    Just over one month ago Broadcom opened up their VideoCore IV 3D graphics driver stack and now it's been brought to work on the Raspberry Pi low-cost ARM board -- to the extent that it can run Quake III...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite

  • #2
    Wait, what?

    Getting the open stack running requires rebuilding the Raspberry Pi's kernel, which allegedly takes about 12 hours on this slow ARMv6 hardware and it's recommended to overclock the Pi for speeding up the process.
    Smart enough to figure out how to get 3D acceleration working on a RPi, but not smart enough to learn how to cross compile?

    Comment


    • #3
      Originally posted by willmore View Post
      Smart enough to figure out how to get 3D acceleration working on a RPi, but not smart enough to learn how to cross compile?
      He's perfectly smart enough, but chose to write one set of instructions so that everybody with a Pi could do it, rather than writing several sets of instructions for cross-compiling depending on which host OS the reader is using.

      The instructions in the blog post also note that one can get better framerates by cross-compiling.

      Comment


      • #4
        Originally posted by archibald View Post
        He's perfectly smart enough, but chose to write one set of instructions so that everybody with a Pi could do it, rather than writing several sets of instructions for cross-compiling depending on which host OS the reader is using.

        The instructions in the blog post also note that one can get better framerates by cross-compiling.
        Eh? How does that work? Maybe if you cross compile with a different (presumably newer) GCC than the one that comes with Raspbian? Of course there's no reason why you couldn't just update GCC on your Pi if that was the case.

        Comment


        • #5
          Why didn't he just use an emulator to compile everything?

          Comment


          • #6
            Originally posted by danboid View Post
            Eh? How does that work? Maybe if you cross compile with a different (presumably newer) GCC than the one that comes with Raspbian? Of course there's no reason why you couldn't just update GCC on your Pi if that was the case.
            From http://www.raspberrypi.org/:

            We’re going to use gcc 4.7, as the code generated is 10% faster than with 4.6. 4.8 is 10% faster still, but this is not available on Raspbian. If you cross-compile you can get better frame times.

            Originally posted by schmidtbag View Post
            Why didn't he just use an emulator to compile everything?
            Because then he would have needed to provide instructions on setting up the emulator for various operating systems. I imagine most people can run a build overnight.
            Last edited by archibald; 01 April 2014, 12:30 PM.

            Comment


            • #7
              Originally posted by schmidtbag View Post
              Why didn't he just use an emulator to compile everything?
              Even on very fast systems Qemu emulating a Pi is not faster than the native Pi.

              Comment


              • #8
                Originally posted by Vim_User View Post
                Even on very fast systems Qemu emulating a Pi is not faster than the native Pi.
                I haven't tried it myself but isn't that just because it deliberately limits the speed? I figure you could unlock the speed.

                Comment


                • #9
                  Originally posted by Vim_User View Post
                  Even on very fast systems Qemu emulating a Pi is not faster than the native Pi.
                  Uh, no. It is much much faster than native to chroot into an ARM userspace using qemu. It's also much less fragile and prone to breakage than crosscompiling.

                  Comment


                  • #10
                    Originally posted by FishB8 View Post
                    Uh, no. It is much much faster than native to chroot into an ARM userspace using qemu. It's also much less fragile and prone to breakage than crosscompiling.
                    How would you chroot into an ARM userspace on a x86 machine? You would have to run a full ARM CPU emulation, which can by definition not use hardware virtualization on a x86 CPU, making it slower than the real hardware.

                    Comment

                    Working...
                    X