3 ms·

Tinkerboard has amazingly performant GPU. Peak performance is 81.6GFlops, comparable to mid-range desktop GPUs from 2007 (e.g. GeForce 8400 GS had 67 GFlops, Ge

Tinkerboard has amazingly performant GPU. Peak performance is 81.6GFlops, comparable to mid-range desktop GPUs from 2007 (e.g. GeForce 8400 GS had 67 GFlops, GeForce 8600 GT had 114 GFlops). It also supports 4k HDMI output resolution. RPi is more compatible i.e. the software stack supports OpenGL. But for cases where it’s OK to code against GLES, Mali-T764 is awesome. I once used NanoVG to build a very nice looking rich GUI, with alpha transparency, animated state transitions, etc. Moreover, it consumes practically no CPU time, because everything is hardware accelerated.

craftyguy 9y ago
You mean Mali and not Mail? If so, boooo proprietary GL stacks. It seems like everyone wants to continue to follow PowerVR's lead, which is extremely unfortunate.
- Const-me 9y ago
  Yes, it’s Mali. Thanks for the correction. Yeah, pretty much all of them are proprietary.
2bitencryption 9y ago
does it require codes to unlock native x264 processing, like the RBP does (or did, back when I used it)? Also, does it have hardware support for HEVC? My poor RBP 2 can't handle HEVC at all.
- Const-me 9y ago
  Unfortunately I don’t know. The product I was working on doesn’t need video playback.
- flyinghamster 9y ago
  In my experience with the Pi, H.264 is baked-in, but you need a license key for MPEG-2 (a necessity if you're dealing with ATSC footage) or VC-1.
elcritch 9y ago
If the Mali-T764’s support GLES and provides the correct libraries you can compile an embedded version of QT5 which runs directly on GLES [cf 0, for an RPi example]. Though the NanoVG seems more fun! Edit: grammar 0: https://wiki.qt.io/RaspberryPi2EGLFS https://wiki.qt.io/RaspberryPi2EGLFS
- Const-me 9y ago
  Right, I have evaluated QT. There were reasons why I decided not use it in that project. 1. Licensing. Their commercial license was prohibitively expensive for the project. And their open source license was too limited for our purposes. 2. I wanted the software to work on top of bare Linux kernel, i.e. no desktop managers, no compositors, no mouse pointer. Also I needed to render different stuff to 2 displays at the same time, QT can’t do that. The GUI wasn’t too complex, just a handful of screens on a 7” 800x480 DSI touch screen, plus simple 2D vector graphics on an external 4k HDMI display. That is why I was able to use lower-level stack without spending too much time on it. I only used C++ for DRM/KMS and NanoVG, everything higher level is in C#, running on .NET Core. BTW, the most time-consuming part was on-screen keyboard for the “Connect to WiFi” screen, and soft keyboards are only available in commercial QT.

craftyguy 9y ago

You mean Mali and not Mail? If so, boooo proprietary GL stacks. It seems like everyone wants to continue to follow PowerVR's lead, which is extremely unfortunate.

Const-me 9y ago
Yes, it’s Mali. Thanks for the correction. Yeah, pretty much all of them are proprietary.

2bitencryption 9y ago

does it require codes to unlock native x264 processing, like the RBP does (or did, back when I used it)? Also, does it have hardware support for HEVC? My poor RBP 2 can't handle HEVC at all.

Const-me 9y ago
Unfortunately I don’t know. The product I was working on doesn’t need video playback.
flyinghamster 9y ago
In my experience with the Pi, H.264 is baked-in, but you need a license key for MPEG-2 (a necessity if you're dealing with ATSC footage) or VC-1.

elcritch 9y ago

If the Mali-T764’s support GLES and provides the correct libraries you can compile an embedded version of QT5 which runs directly on GLES [cf 0, for an RPi example]. Though the NanoVG seems more fun! Edit: grammar 0: https://wiki.qt.io/RaspberryPi2EGLFS https://wiki.qt.io/RaspberryPi2EGLFS

Const-me 9y ago
Right, I have evaluated QT. There were reasons why I decided not use it in that project. 1. Licensing. Their commercial license was prohibitively expensive for the project. And their open source license was too limited for our purposes. 2. I wanted the software to work on top of bare Linux kernel, i.e. no desktop managers, no compositors, no mouse pointer. Also I needed to render different stuff to 2 displays at the same time, QT can’t do that. The GUI wasn’t too complex, just a handful of screens on a 7” 800x480 DSI touch screen, plus simple 2D vector graphics on an external 4k HDMI display. That is why I was able to use lower-level stack without spending too much time on it. I only used C++ for DRM/KMS and NanoVG, everything higher level is in C#, running on .NET Core. BTW, the most time-consuming part was on-screen keyboard for the “Connect to WiFi” screen, and soft keyboards are only available in commercial QT.