Announcement

Collapse
No announcement yet.

How To Help Improve, Develop Mesa Drivers

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

  • phoronix
    started a topic How To Help Improve, Develop Mesa Drivers

    How To Help Improve, Develop Mesa Drivers

    Phoronix: How To Help Improve, Develop Mesa Drivers

    If you aren't satisfied with seeing Mesa lag far behind the latest OpenGL standard and come up short when in the areas of performance and features compared to some of the proprietary graphics drivers, they always welcome additional help...

    http://www.phoronix.com/vr.php?view=MTE1NTY

  • Hamish Wilson
    replied
    Originally posted by whitecat View Post
    Don't forget to tell manually to ETQW how many VRAM you have, because it fails to detect automatically and set only 128 MB of VRAM
    Already have that covered:

    /usr/local/games/etqw/etqw.x86 +set sys_videoRam 1024

    Leave a comment:


  • whitecat
    replied
    Originally posted by Hamish Wilson View Post
    Here are my complete system specifications:
    Operating System: Fedora 16 Linux
    Video Card: AMD Radeon HD 4670
    Memory: 4 Gigabytes
    Processor: AMD Sempron CPU 2.7 Ghz
    Hard Drive: 2 TB Western Digital Caviar Green
    Don't forget to tell manually to ETQW how many VRAM you have, because it fails to detect automatically and set only 128 MB of VRAM.

    Originally posted by Hamish Wilson View Post
    Still, now I am curious to if I will get any speed up when I upgrade to Fedora 18 in the fall.
    For sure! Believe me

    Leave a comment:


  • Hamish Wilson
    replied
    Originally posted by whitecat View Post
    Interesting, on my hardware (Pentium [email protected],7GHz, 2 Go RAM, HD4850) I remember that ETQW worked on F16 but was too slow to be playable. With F17 that was much better, but the current upstream is for me the first "version" really playable. ETQW runs at 30~60 FPS in 1680*1050 (low details), without bugs or crash obviously (except with Linux 3.5).
    It does works for me with the latest Kernel and Mesa drivers available in the Fedora 16 repositories. Granted, I had to set r_useIndexBuffers to 1 in .etqwctl/base/etqwconfig.cfg to get everything running smoothly and I am playing the game at only 1280x720 (with default graphics settings). Not sure what FPS I am getting as I neglected to activate the FPS meter, but it is certainly playable.

    Here are my complete system specifications:
    Operating System: Fedora 16 Linux
    Video Card: AMD Radeon HD 4670
    Memory: 4 Gigabytes
    Processor: AMD Sempron CPU 2.7 Ghz
    Hard Drive: 2 TB Western Digital Caviar Green

    Still, now I am curious to if I will get any speed up when I upgrade to Fedora 18 in the fall.

    Leave a comment:


  • Lynxeye
    replied
    Originally posted by Nille View Post
    Blender and many other Software that build the UI with OpenGL. But thats not the point. Someone has implement this feature but it is ignored from the other devs.
    Yes it happens that devs ignore stuff, but that's not because they don't like it but more that no one has had the time to finish this up for inclusion. To get something into mesa you need someone actively driving stuff forward. In the GL_SELECT case there was a pretty good implementation that was even pushed to a branch upstream, but after that there was no one who did the work to cut the last rough edges.

    If this is really a thing that bothers you, why don't you go ahead and try to get it mainline? It shouldn't be too hard, as it was nearly finished. Just get on the Mailing List and ask what other people think, what has to be done to get this integrated. Then if you fix up the last bits I think there will be no one that blocks this from inclusion. It's just not that devs go there and say: "oh, there's this code to enable a feature I never used and never tested, but ok I'll commit this". You need people to drive things forward, even if it's sometimes just a minor push that's needed to get things going.

    So please don't just talk about "the devs", this is not a proprietary project, this is open source, so you can easily be a dev, too.

    Leave a comment:


  • Nille
    replied
    Originally posted by curaga View Post
    Who uses that? It's old functionality, and a sw fallback in practically every driver.
    Blender and many other Software that build the UI with OpenGL. But thats not the point. Someone has implement this feature but it is ignored from the other devs.
    Last edited by Nille; 08-08-2012, 07:16 AM.

    Leave a comment:


  • curaga
    replied
    Originally posted by Nille View Post
    Its really sad that patches getting tested but are never comitted (e.g. GL_SELECT Patches for radeon) :/ Since over one year the code is there ( and from many ppl tested ) but no dev what to look at this :/
    Who uses that? It's old functionality, and a sw fallback in practically every driver.

    Leave a comment:


  • ssam
    replied
    Originally posted by entropy View Post
    Then there was this thread which died unfortunately (but not unexpected):

    Sponsor An Open Source Driver Dev
    it sounds like there is already money available through the xorg evoc. Just need to find some people to sign up to code.

    Leave a comment:


  • whitecat
    replied
    Originally posted by Hamish Wilson View Post
    Sorry to burst your bubble, but ET:QW is running for me fine on the stock Mesa and R600 Gallium3D drivers currently available for Fedora 16. Just make sure that r_useIndexBuffers is set to 1 in .etqwctl/base/etqwconfig.cfg and you should be golden.
    Interesting, on my hardware (Pentium [email protected],7GHz, 2 Go RAM, HD4850) I remember that ETQW worked on F16 but was too slow to be playable. With F17 that was much better, but the current upstream is for me the first "version" really playable. ETQW runs at 30~60 FPS in 1680*1050 (low details), without bugs or crash obviously (except with Linux 3.5).

    Leave a comment:


  • 89c51
    replied
    Originally posted by 9a3eedi View Post
    I am fairly proficient in C/C++ but I'm pretty sure that's not enough to get into Mesa development

    In general I always found it difficult to get into opensource development, but Mesa probably is even more difficult because of its low level nature.
    If you ask at the IRC or the mailing list people there will most certainly guide you on where to start, give you an introductory task or whatever. The TODOs that Michael posted is a place to start.

    Leave a comment:

Working...
X