ODROID-N2was announced last February for $63 (2GB RAM), and $79 (4GB RAM), but Hardkernel was not quite ready to take orders at the time. One of the good news is that the 4GB RAM is nowavailable for pre-orderwith shipping scheduled to start on April 3.
Another good news is on the software side with Hardkernelhaving releasedthe userland Mali-G52 Wayland driver. It does not work well with Linux 4.9 due to incomplete DRM implementation, but it goes work with Linux 5.0 plus some modifications as further discussed in the aforelinked forum thread.

The screenshot above, courtesy of odroid forum member memeka , shows ODROID-N2 running Ubuntu 18.04 + Gnome3 + Linux 5.0 on top of Wayland with GPU drivers providing acceleration as shown by glmark2-es2-wayland test program.
The benchmark results are pretty impressive:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
===
===
===
===
===
===
===
===
===
===
===
===
===
===
===
===
===
===
=
glmark2
2014。03
+
GIT20150611
。fa71af2d
===
===
===
===
===
===
===
===
===
===
===
===
===
===
===
===
===
===
=
OpenGL
Information
gl_vendor
:
ARM
GL_RENDERER
:
Mali
-
G52
GL_VERSION
:
OpenGL
es
3。2
v1
。r16p0
-
01rel0.2943fc4ef9657d91ee32c9a58dec6cd2
===
===
===
===
===
===
===
===
===
===
===
===
===
===
===
===
===
===
=
[[
build
这是给予的
use
-
vbo
=
错误的
:
FPS
:
961
FrameTime
:
1。041
ms
[[
build
这是给予的
use
-
vbo
=
true
:
FPS
:
1592年
FrameTime
:
0.628
ms
[[
texture
这是给予的
texture
-
filter
=
最近
:
FPS
:
1491
FrameTime
:
0.671
ms
[[
texture
这是给予的
texture
-
filter
=
linear
:
FPS
:
1477
FrameTime
:
0.677
ms
[[
texture
这是给予的
texture
-
filter
=
mipmap
:
FPS
:
1524
FrameTime
:
0.656
ms
[[
shading
这是给予的
shading
=
gouraud
:
FPS
:
1151
FrameTime
:
0.869
ms
[[
shading
这是给予的
shading
=
blinn
-
phong
-
inf
:
FPS
:
1215
FrameTime
:
0。823
ms
[[
shading
这是给予的
shading
=
phong
:
FPS
:
1043
FrameTime
:
0.959
ms
[[
shading
这是给予的
shading
=
cel
:
FPS
:
1126
FrameTime
:
0.888
ms
[[
bump
这是给予的
bump
-
render
=
high
-
poly
:
FPS
:
514
FrameTime
:
1。946
ms
[[
bump
这是给予的
bump
-
render
=
normals
:
FPS
:
1976
FrameTime
:
0.506
ms
[[
bump
这是给予的
bump
-
render
=
height
:
FPS
:
1777
FrameTime
:
0.563
ms
[[
效果2d
这是给予的
核心
=
0
,,,,
1
,,,,
0
;
1
,,,,
-
4
,,,,
1
;
0
,,,,
1
,,,,
0
;
:
FPS
:
1139
FrameTime
:
0.878
ms
[[
效果2d
这是给予的
核心
=
1
,,,,
1
,,,,
1
,,,,
1
,,,,
1
;
1
,,,,
1
,,,,
1
,,,,
1
,,,,
1
;
1
,,,,
1
,,,,
1
,,,,
1
,,,,
1
;
:
FPS
:
383
FrameTime
:
2。611
ms
[[
pulsar
这是给予的
light
=
错误的
:
quads
=
5
:
texture
=
错误的
:
FPS
:
2096
FrameTime
:
0。477
ms
[[
桌面
这是给予的
模糊
-
半径
=
5
:
effect
=
模糊
:
通过
=
1
:
separable
=
true
:
windows
=
4
:
FPS
:
389
FrameTime
:
2.571
ms
[[
桌面
这是给予的
effect
=
shadow
:
windows
=
4
:
FPS
:
788
FrameTime
:
1。269
ms
[[
buffer
这是给予的
columns
=
200
:
interleave
=
错误的
:
update
-
dispersion
=
0.9
:
update
-
fraction
=
0.5
:
update
-
method
=
map
:
FPS
:
103
FrameTime
:
9。709
ms
[[
buffer
这是给予的
columns
=
200
:
interleave
=
错误的
:
update
-
dispersion
=
0.9
:
update
-
fraction
=
0.5
:
update
-
method
=
subdata
:
FPS
:
129
FrameTime
:
7。752
ms
[[
buffer
这是给予的
columns
=
200
:
interleave
=
true
:
update
-
dispersion
=
0.9
:
update
-
fraction
=
0.5
:
update
-
method
=
map
:
FPS
:
158
FrameTime
:
6。329
ms
[[
ideas
这是给予的
speed
=
期间
:
FPS
:
356
FrameTime
:
2。809
ms
[[
jellyfish
这是给予的
<
default
>
:
FPS
:
979
FrameTime
:
1.021
ms
[[
地形
这是给予的
<
default
>
:
FPS
:
52
FrameTime
:
19。231
ms
[[
shadow
这是给予的
<
default
>
:
FPS
:
437
FrameTime
:
2.288
ms
[[
refract
这是给予的
<
default
>
:
FPS
:
88
FrameTime
:
11。364
ms
[[
conditionals
这是给予的
fragment
-
steps
=
0
:
vertex
-
steps
=
0
:
FPS
:
1769
FrameTime
:
0.565
ms
[[
conditionals
这是给予的
fragment
-
steps
=
5
:
vertex
-
steps
=
0
:
FPS
:
1769
FrameTime
:
0.565
ms
[[
conditionals
这是给予的
fragment
-
steps
=
0
:
vertex
-
steps
=
5
:
FPS
:
1853
FrameTime
:
0.540
ms
[[
function
这是给予的
fragment
-
complexity
=
low
:
fragment
-
steps
=
5
:
FPS
:
1783
FrameTime
:
0.561
ms
[[
function
这是给予的
fragment
-
complexity
=
中等的
:
fragment
-
steps
=
5
:
FPS
:
1726
FrameTime
:
0.579
ms
[[
loop
这是给予的
fragment
-
loop
=
错误的
:
fragment
-
steps
=
5
:
vertex
-
steps
=
5
:
FPS
:
1715
FrameTime
:
0.583
ms
[[
loop
这是给予的
fragment
-
steps
=
5
:
fragment
-
uniform
=
错误的
:
vertex
-
steps
=
5
:
FPS
:
1650
FrameTime
:
0。606
ms
[[
loop
这是给予的
fragment
-
steps
=
5
:
fragment
-
uniform
=
true
:
vertex
-
steps
=
5
:
FPS
:
1728
FrameTime
:
0.579
ms
===
===
===
===
===
===
===
===
===
===
===
===
===
===
===
===
===
===
=
glmark2
Score
:
1119
===
===
===
===
===
===
===
===
===
===
===
===
===
===
===
===
===
===
=
|
I’ve never seen such as high score (1,119 points) on Arm hardware. But at the same time, I’ve never run the wayland version of the benchmark, so that may partially explain it. For reference,RockPro64 RK3399 SBCgets 48 points in the onscreen test (default), and 201 points in the offscreen test. I could not find results for glmark2-es2-wayland for Rockchip RK3399 despitebeing supported。因此,我们必须查看Mali-G52MP GPU的一部分是更高的分数,而Wayland在XORG/X11上的使用是哪一部分。

Jean-Luc于2010年启动了www.yabo188.vipCNX软件,作为兼职工作,然后辞去了软件工程经理的工作,并开始写每日新闻,并于2011年晚些时候全职审查。
As far as I remember from the N1, glmark2-es2-wayland results were in the 800-900 range for RK3399, but with a 32bit blob and userland. But I doubt it would have been bigger on 64bit userland.
韦兰,是的!干得好,像往常一样!:))
>glmark2-es2-wayland results were in the 800-900 range for RK3399
Jean-Luc在测试时如何只能获得48分?这仅仅是X11和Wayland之间的区别吗?
Two words: buffer management. For the on-screen tests, the presentation part of the pipeline has been the bane of most GLX/EGL stacks. It doesn’t matter how quick a GPU is, if the presentation part does memcpy between FBs/RTs/pixelbuffers/etc. For the off-screen tests, one’d need to profile, but I’d wager some buffer management shenanigans at play as well. Wayland traditionally solves the presentation part.
For the onscreen tests, I think the maximum framerate is also limited by vsync. For example if output if 1080p50, the benchmarks may not go over 50 fps.
That’s right, vsync is a factor in on-screen. I was referring to the registered difference in performance of N1 under wayland and x11 whether on-screen or off-screen.
I half recall reading some where that the drivers only work on the VPU, is that right?
我们在这里谈论的是GPU驱动亚博体育官下载程序。即3D图形加速度。
The VPU is for video encoding/decoding.
I’d suggest taking Linux 5.x benchmarks with a pinch of salt, as apparently a lot of hardware benchmark a lot higher on Linux 5.x, but there’s no real world performance gain.
真的?我在phoronix上看到了一些Linux 5.0基准,并且某些测试的性能下降了
显然至少在某些手臂硬件上。不确定其他平台。亚博体育官下载
what about 4k opengles?
glmark should support something like offscreen rendering. so it should be possible to run test with 4k resolution
To date, a large majority of MALI models, can support Wayland. I am just as curious, to see turning Kodi with a VPU able to be used, something that I doubt following my many tests.
如果Amlogic Kern编解码器仍然可用el 5.0, we will have to use Framebuffer, or Xorg.
there are no x11 drivers, arm stopped providing them in recent mali DDKs.
对于N2,没有5.0上的Amlogic编解码器,但它们正在为较旧的Amlogic Soc(S805,S905)工作。因此,我敢肯定,N2也很快就会出现。
Kodi is ok on wayland on gbm.
I did not know for “X11”, remains to see if an buildroot has AMLogic is planned officially, with the use of the Framebuffer and these codecs.
I doubt the Dream team is designing their own video accelerator for the “Dreambox One”, I think, they relied on the ports (/dev/amstream, /dev/amvideo…), and official codecs.
Very bad radiator design, board will overheat during benchmark and any CPU intensive task.
BS
LOL. Don’t be ridiculous.
I assume this is another joke on you