JohnnyonFlame has quit [Read error: Connection reset by peer]
JohnnyonFlame has joined #etnaviv
_whitelogger has joined #etnaviv
lilstevie has quit [*.net *.split]
MaxPower2005 has joined #etnaviv
lilstevie has joined #etnaviv
lynxeye has joined #etnaviv
T_UNIX has joined #etnaviv
lynxeye has quit [Remote host closed the connection]
lynxeye has joined #etnaviv
pcercuei has joined #etnaviv
smurray has quit [*.net *.split]
smurray has joined #etnaviv
JohnnyonFlame has quit [Read error: Connection reset by peer]
JohnnyonFlame has joined #etnaviv
JohnnyonFlame has quit [Ping timeout: 240 seconds]
JohnnyonF has joined #etnaviv
cphealy has joined #etnaviv
pcercuei has quit [Quit: brb]
pcercuei has joined #etnaviv
ad__ has joined #etnaviv
<ad__>
hi all
karolherbst has quit [Quit: duh 🐧]
<ad__>
is there a particular version from where you can suggest to switch to etnaviv from imx-gpu-viv ?
karolherbst has joined #etnaviv
MaxPower2005 has quit [Quit: ChatZilla 0.9.94 [SeaMonkey 2.49.5/20190805002510]]
Chewi has quit [Ping timeout: 260 seconds]
JohnnyonFlame has joined #etnaviv
JohnnyonF has quit [Ping timeout: 258 seconds]
<cphealy>
ad: particular version of what? Kernel? Mesa? Something else?
<cphealy>
If your talking about Mesa, I would suggest using the latest released version (Mesa 20.2) Likewise, for the kernel, go with the latest version you can run on your HW.
<ad__>
cphealy, ok, was referring to kernel, i.e. for a 5.4 (LTS) would be possible to use etnaviv to replace mxc-gpu-viv ?
cengiz_io5 has joined #etnaviv
<ad__>
also, i think both are available in the imx tree, so one should be able to test both, right ?
<cphealy>
ad: I'm using 5.4 with the i.MX6q (GC2000), i.MX6qp (GC3000), and i.MX8M (GC7000lite). That said, I intend on upgrading soon for reasons unrelated to etnaviv.
<ad__>
cphealy, thanks a lot
cengiz_io has quit [Ping timeout: 260 seconds]
cengiz_io5 is now known as cengiz_io
<cphealy>
What kernel you use likely depends on what your use cases are and what SoC you are working with though.
<marex>
ad__: 5.4 at least, mesa 20.1.y (latest) at least
<marex>
ad__: which SoC are you on ?
<marex>
ad__: and it is always good to switch from the crappy blob
<ad__>
ok i am on imx6dual, was looking about mxc-gpu-viv improvements from 4.9 linux-fslc to 5.4, then i tested a mainline kernel on sabrelite and seen it is using etnaviv, so was trying to understand if etnaviv performance are better/worst from vivante driver
<marex>
ad__: just use mainline on mx6d
<ad__>
hi marex :)
<ad__>
well, woudl be ok a stable 5.4.y (LTS) rebasing imx stuff on, so to have last improvements also for mxc-gpu-viv (so te be able to test both, if it has sense) ?
Chewi has joined #etnaviv
<cphealy>
ad: The i.MX6dual uses the GC2000. Earlier this year, I benchmarked the GPU using glmark2-es2 on 5.4 with Mesa 19.3.2 and compared against the NXP Vivante blob driver. glmark2-es2 scores showed that etnaviv was a few percent lower than the Vivante blob driver overall, but when looking at the individual tests it appears that most tests are faster with etnaviv except for the texturing tests where etnaviv is considerably slower
<cphealy>
than the Vivante blob. If the texturing issue is resolved with etnaviv, then the overall score for etnaviv would be faster than the Vivante blob driver.
<ad__>
cphealy, great, thanks a lot for these precious infos
<ad__>
and marex, thanks a lot :)
<cphealy>
Question for all on here: This knowledge about etnaviv vs the Vendor blob performance feels like something that should be documented and periodically updated somewhere as it's a common question. Where would be a good place to put this knowledge?
<cphealy>
Perhaps a place for putting a transition guide of something akin to that too as there are things that are different from a coding standpoint when switching between the drivers. For example, video import is different between Vivante and etnaviv in that Vivante uses some vendor proprietary GL extensions while etnaviv uses existing Khronos extensions.
<marex>
ad__: does imx blob even work on 5.4.y ?
<ad__>
marex ?? havent yet tested, but, is it broken in 5.4 ? compraed to 4.9, there are abouot 80 patches ov varipous improvements
<marex>
ad__: I didnt use the blob for years, I only ever use it on some archaic heavily patched vendorkernel where it barely works if I need to see what it does ; but luckily I dumped all the command streams by now, so not even that is needed anymore
<ad__>
well, i believe some out there wants to use imx blob since is supported from nxp
<ad__>
for any issue, nxp says "out _2.0.0 bla bla" is only supported
<marex>
ad__: supported how ? like on the imx community ?
<marex>
I never found any really useful answers there
<marex>
sorry
<marex>
cphealy: probably the visucore wiki, or elinux wiki
<marex>
cphealy: also, some sort of word diff of dEQP-GLES*.perf* tests would help
<marex>
then it would be clear exactly what is slower and what is faster
lynxeye has quit [Quit: Leaving.]
<cphealy__>
marex: thanks for the recommendation. I'll look at that.
T_UNIX has quit [Quit: Connection closed for inactivity]