<suniel>
what am i doing wrong, please suggest. Thanks
prefixcactus has joined #linux-sunxi
<gediz539>
suniel: I'm not sure but "Gallium KMSRO" may be required
<suniel>
gediz539, right now i am using "lima,kmsro"
<gediz539>
strange. i think it shouldn't fall back to softpipe when kmsro is available.
<gediz539>
in which environment did you get/compile your tools?
<gediz539>
i'm using buildroot enabled following to make lima work on A13: BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_KMSRO, BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_LIMA
<MoeIcenowy>
suniel: what kernel do you utilize
<suniel>
gediz539, I am using yocto
<suniel>
MoeIcenowy: i am using kernel 5.10.x
<MoeIcenowy>
suniel: did you configure KMS?
<MoeIcenowy>
(I mean the display provided by sun4i-drm driver
Danct12 has joined #linux-sunxi
<MoeIcenowy>
(check /dev/dri, and seek for both card0 and card1
<MoeIcenowy>
(2 cards should exist, one for display, another for Lima 3D
<suniel>
yes noth card0 and card1 are detected. as far as kernel part is concerned all configs related to GPU and display are enabled
<suniel>
i am suspecting something wrong with my user space
<MoeIcenowy>
then is renderD128 existing?
<MoeIcenowy>
existed *
<MoeIcenowy>
and how's renderD128's permission?
<MoeIcenowy>
it should be accessable by the user running glmark2
<suniel>
renderD128 exists and has re-rw-rw permissions. I am running as root
mmarc__ has quit [Remote host closed the connection]
kaspter has quit [Quit: kaspter]
gediz539 has quit [Quit: Leaving]
eduardas has joined #linux-sunxi
faruk has quit [Quit: Leaving]
reinforce has quit [Quit: Leaving.]
ldevulder has quit [Remote host closed the connection]
ldevulder has joined #linux-sunxi
<jernej>
apritzel: so you have working H616 USB setup?
<apritzel>
again! :-D
<apritzel>
jernej: well, I do this manual sequence in U-Boot to make it work when booting from SD card
<apritzel>
I have a plan for a patch to the Linux USB PHY driver to make this proper
<apritzel>
if things go well, this should go out tonight
<apritzel>
(but don't hold your breath on it)
<jernej>
no problem :)
<apritzel>
the alternative could be a firmware (U-Boot) patch, because all we need is to clear SIDDQ in PHY2, and this stays across PHY and HCI reset, apparently
<apritzel>
(I guess because this is actually in this PMU, which might not be covered by the PHY or HCI resets)
cmeerw has joined #linux-sunxi
yann has quit [Ping timeout: 260 seconds]
jstefanop has quit [Remote host closed the connection]
jstefanop has joined #linux-sunxi
gaston1980 has joined #linux-sunxi
Jin^eLD has quit [Ping timeout: 246 seconds]
tnovotny has quit [Quit: Leaving]
yann has joined #linux-sunxi
netlynx has joined #linux-sunxi
netlynx has quit [Changing host]
netlynx has joined #linux-sunxi
sunshavi has quit [Read error: Connection reset by peer]
sunshavi has joined #linux-sunxi
suniel has quit [Ping timeout: 240 seconds]
choozy has joined #linux-sunxi
gaston1980 has quit [Ping timeout: 240 seconds]
mmarc__ has joined #linux-sunxi
gaston1980 has joined #linux-sunxi
mmarc__ has quit [Remote host closed the connection]