Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
Graphics Be Open Source Software Upgrades X Hardware BSD Linux

Linux Support Fades For 3Dfx Voodoo, Rage 128, VIA 330

An anonymous reader writes "The developers behind the Mesa 3D graphics library, which provides the default graphics driver support for most hardware on Linux (and BSD/Solaris), has ended their support for older hardware. Being removed from Mesa (and therefore versions of Linux distributions) is support for hardware like the 3Dfx Voodoo, Intel i810, ATI Rage, and S3 Savage graphics processors. Also drivers being dropped were for Matrox and VIA graphics. Mesa developers also decided it's time to end support for the BeOS operating system. Dropping this code lowered the developers' responsibility by some 100k L.O.C., so maybe we will see GL3 support and OpenCL in Linux a bit sooner."
This discussion has been archived. No new comments can be posted.

Linux Support Fades For 3Dfx Voodoo, Rage 128, VIA

Comments Filter:
  • by hendrikboom ( 1001110 ) on Saturday August 27, 2011 @11:38AM (#37227722)

    Sounds like it's time for a legacy fork for old machines. Or maybe just keeping old versions alive, the way Linux distros do with other libraries.

    -- hendrik

  • Older machines? (Score:1, Interesting)

    by DogDude ( 805747 ) on Saturday August 27, 2011 @11:57AM (#37227856)
    I thought that one of Linux's claims to fame was that you could run it on ancient hardware? These cards aren't anywhere close to ancient, and are actively in use in who knows how many machines.
  • Re:...And? (Score:5, Interesting)

    by canajin56 ( 660655 ) on Saturday August 27, 2011 @12:07PM (#37227930)
    Not running the latest software? Doom 3 running on a Voodoo 2 [3dfxzone.it] ;)
  • Re:...And? (Score:5, Interesting)

    by wagnerrp ( 1305589 ) on Saturday August 27, 2011 @12:25PM (#37228036)
    Try as we might, we just can't manage to get you people to migrate to more modern hardware. Frozen and unchanging code means exactly that, the code is not being improved in any manner. We recently redid both the UI and video rendering interfaces. Say we want to further add some animation support to the video renderer for use on the OSD, that code needs to be written for each of Xshm, Xv, OpenGL, VDPAU, VAAPI, XvMC, and PVR-350 framebuffer output. In addition, that's primarily the work of one single guy. XvMC hasn't been supported on any useful hardware sold in the last couple years, and the PVR-350 hasn't been sold for over half a decade. So, we can either continue to support all of those modes, or we can drop the "old cruft" and maybe the people who aren't so cheap as to be unwilling to spend $20 on a video card can have something that looks a bit nicer.

"Say yur prayers, yuh flea-pickin' varmint!" -- Yosemite Sam