• Locked Locked
  • Replies 18 replies
  • Subscribers 136 subscribers
  • Views 28816 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Mali GPU development boards

guestposter guestposter
Note: This was originally posted on 12th October 2009 at http://forums.arm.com

While there are a variety of Mali GPU licensees currently designing Mali GPUs into their SoCs, there are not necessarily many development boards available to the general public.

In order to provide application developers on Mali GPU-based projects with the hardware they need to get their work done, we would like to gain a strong (and accurate) understanding of what needs to be made available. What are the things you look for in a development platform?
Parents
  • Note: This was originally posted on 3rd November 2009 at http://forums.arm.com

    I have looked at the quick specs of mail, and it looks good, except the mystery of any open specs and/or drivers. I can't determine in detail if it is what I want. I have been bitten before by the "looks nice in the spec sheet" but "severely disappoints you when you actually find all the details, "gotchas" etc." department. I've been bitten by closed OpenGL-ES drivers before that have bugs that you can't verify or fix, or that simply lack the features you need (eg X11 flavor of EGL, TexturefromPixmap extensions etc.), and as your vendor also has restricted source access - they cannot provide the changes, nor can you "help yourself", as it's a closed blob. The Hardware is capable of it, just it has been artificially limited but API libraries on top that you cannot replace, modify or even inspect to see if the bug is yours, or the libraries'.

    I vote for at least open drivers, if not open drivers and specifications (enough specifications needed to modify, improve or fix the driver libraries). Right now such gfx units are in short supply on embedded devices, and I will lean to the open ones almost always as at least any hole I end up in, I can dig myself out of.
Reply
  • Note: This was originally posted on 3rd November 2009 at http://forums.arm.com

    I have looked at the quick specs of mail, and it looks good, except the mystery of any open specs and/or drivers. I can't determine in detail if it is what I want. I have been bitten before by the "looks nice in the spec sheet" but "severely disappoints you when you actually find all the details, "gotchas" etc." department. I've been bitten by closed OpenGL-ES drivers before that have bugs that you can't verify or fix, or that simply lack the features you need (eg X11 flavor of EGL, TexturefromPixmap extensions etc.), and as your vendor also has restricted source access - they cannot provide the changes, nor can you "help yourself", as it's a closed blob. The Hardware is capable of it, just it has been artificially limited but API libraries on top that you cannot replace, modify or even inspect to see if the bug is yours, or the libraries'.

    I vote for at least open drivers, if not open drivers and specifications (enough specifications needed to modify, improve or fix the driver libraries). Right now such gfx units are in short supply on embedded devices, and I will lean to the open ones almost always as at least any hole I end up in, I can dig myself out of.
Children
No data