Linux/TDA2EXEVM: port virtual drm to kernel 4.14

fanok

Expert 2400 points

Part Number: TDA2EXEVM

Tool/software: Linux

hi all,

i want to run virtual drm on J6Entry EVM board, kernel version is 4.14.

now i can port virtual drm from kernel 4.4 to kernel 4.14, and i also modify DTS add vdrm device.

and when kernel boot i can see the /dev/dri/card0 and /dev/vdrm-controller-0 devices.

but when i try to use virtual drm, it goes wrong:

int fd = open("/dev/dri/card0", O_RDWR);

struct gbm_device *display = gbm_create_device(fd);

if (NULL == display)

{

OS_TRACE(("fail to create GBM display\n"));

}

PVR:(Error): [ 71-> 71] < gbm_pvr_create_device():592|ERROR> Failed to create DBM device: No such device [0, ]

it can open success, but when call gbm_create_device() to create device, it goes wrong.

does the libgbm.so need to modify too? does PVR need modify? or else need modify too?

best regards!

over 6 years ago

0 Ramprasad over 6 years ago

TI__Mastermind 30480 points

Hi fanok,

Can you check if this is the issue?

http://processors.wiki.ti.com/index.php/Virtual_DRM_:_An_User_Guide_for_Developing_Usecases#I_have_installed_Processor_SDK_Vision_3.04.00.00_with_VDRM_support_and_EVM_boots_up._But_the_weston_log_file_indicates_weston_failed_to_launch._Why.3F

Thanks

RamPrasad

0 fanok over 6 years ago in reply to Ramprasad

Expert 2400 points

hi RamPrasad,

i don't use Waland and weston, and there is not exist /etc/powervr.ini,

i want to know modify which code file can do the same thing as the following setting?

[weston]
DbmDriverName=vdrm

best regards!

0 Ramprasad over 6 years ago in reply to fanok

TI__Mastermind 30480 points

Hi fanok,

Which filesystem is used here. Is it from PSDKLA5.03 or from VISIONSDK3.x? If you don't have a /etc/powervr.ini you can create this with these as contents.

[default]
#WindowSystem=libpvrws_WAYLAND.so

[appName]

DbmDriverName=vdrm

Here , appName is the name of the application you are launching? If you are not using wayland/weston, you can first try with kmscube.

We have tested kmscube on vDRM with this patch applied.

http://git.ti.com/glsdk/kmscube/commit/456cabc661caac5c60729751d45efd668faa8e97

Thanks

Ramprasad

0 fanok over 6 years ago in reply to Ramprasad

Expert 2400 points

hi Ramprasad,

the file system is from PSDK.

if i add /etc/powervr.ini config file, should i execute pvrsrvinit in rcS?

now my rcS as following:

#! /bin/sh

insmod lib/modules/4.14.24-01358-g403020b/extra/pvrsrvkm.ko

pvrsrvctl --start --no-module&

....

but not execute pvrsrvinit.

best regards!

0 Ramprasad over 6 years ago in reply to fanok

TI__Mastermind 30480 points

You don't need to insert modules manually,

rc5 scripts will install. You can check this after boot on target

$lsmod | grep pvr

0 Ramprasad over 6 years ago in reply to Ramprasad

TI__Mastermind 30480 points

Hi fanok,

Are you not using vision-sdk at all here and only PSDKLA? In that case vDRM is not going to work.

vDRM is currently supported with vision-sdk's firmware running on M4 and display is controlled by M4.

In PSDKLA case, display is controlled by A15 and vDRM feature is not available here.

Ramprasad

0 fanok over 6 years ago in reply to Ramprasad

Expert 2400 points

hi Ramprasad ,

The purpose of porting vitual drm into kernel 4.14 is using visionSDK, but now vitual drm work on A15 is not correct, so the buffer can not transfer to M4 side to display by DSS.

i disable omapdrm, enable vdrm, then i write an app that is similar with Kmscube app.

when call gbm_create_device() API, it occurred error that the previous mention.

best regards!

0 Ramprasad over 6 years ago in reply to fanok

TI__Mastermind 30480 points

Hi fanok,

I still didn't understand if you have ported vision-sdk-linux to 4.14 and taken care of all patches. Please confirm.

Can you also let me know if the sgx-um binaries now is from PSDKLA5.03 or from the vision-sdk?

Please share the details of commit-ID of omap5-sgx-ddk-um-linux

Thanks

Ramprasrad

0 fanok over 6 years ago in reply to Ramprasad

Expert 2400 points

hi Ramprasrad,

thanks for your reply, kernel 4.14 is not support virtual drm, and kernel 4.4 is support it , so we

get the virtual drm patchs from kernel 4.4, then port it into kernel 4.14. fix some compile error,

then running visionsdk IPU2 firmware by remoteproc module.

omap5-sgx-ddk-um-linux is from PSDK,

branch is: ti-img-sgx/1.14.3699939/k4.1

commit ID is :

commit d2b3959738cfcc6209e8e882d1989de790866c8f
Author: Denys Dmytriyenko <denys@ti.com>
Date: Fri Nov 10 18:55:26 2017 -0500

srvkm/common/devicemem.c: suppress implicit fallthrough error in gcc7

Signed-off-by: Denys Dmytriyenko <denys@ti.com>

best regards!

0 Ramprasad over 6 years ago in reply to fanok

TI__Mastermind 30480 points

Hi fanok,

There are some changes required in omap5-sgx-ddk-um-linux to support vDRM.

If you take sgx-um binaries from PSDKLA5.x, it won't support vDRM. Can you try with the sgx-um binaries provided in vision-SDK. Refer the userGuide of vision-sdk on the link

TI has not tried 4.14 kernel for vDRM.

Thanks

Ramprasad

0 fanok over 6 years ago in reply to Ramprasad

Expert 2400 points

hi Ramprasad,

i can not find sgx-um binaries in visionSDK 0304, where can i get it ?

where is the link?

best regards!

0 Ramprasad over 6 years ago in reply to fanok

TI__Mastermind 30480 points

Latest available vision-sdk is v3.07

http://software-dl.ti.com/processor-sdk-vision/esd/TDAx/vision-sdk/latest/index_FDS.html

If you have not vision-sdk earlier , you can not use vDRM with Linux SDK alsone.

Thanks

Ramprasad

0 fanok over 6 years ago in reply to Ramprasad

Expert 2400 points

hi Ramprasad,

i also can not find any user guide relate to omap5-sgx-ddk-um-linux in visionSDK 0307,

which user guide ?

best regards!

0 Ramprasad over 6 years ago in reply to fanok

TI__Mastermind 30480 points

which version of vision-sdk firmwares you are using now?

Take sgx-um binaries from same vision-SDK.

0 fanok over 6 years ago in reply to Ramprasad

Expert 2400 points

hi Ramprasad,

i use visionSDK 0304, i dont know which dir include the sgx-um binaries?

best regards!

0 Ramprasad over 6 years ago in reply to fanok

TI__Mastermind 30480 points

sgx-um binaries are available in the filesystem provided here.

tisdk-rootfs-image-dra7xx-evm_vsdk_3_4.tar.xz

http://software-dl.ti.com/processor-sdk-vision/esd/TDAx/vision-sdk/03_04_00_00/index_FDS.html

Did you try using this filesystem but migrating only linux kernel to 4.14. and replacing kernel modules and zImage ?

0 fanok over 6 years ago in reply to Ramprasad

Expert 2400 points

hi Ramprasad,

i get pvrsrvkm.ko from tisdk-rootfs-image-dra7xx-evm_vsdk_3_4.tar.xz and replace the current ko file.

but insmod fail. log as following:

[ 2.470543] pvrsrvkm: disagrees about version of symbol module_layout
insmod: can't insert 'lib/modules/4.14.24-01358-g403020b/extra/pvrsrvkm.ko': invalid module format

i think this ko is not match to current kernel. i guess i need recompile PVR using kernel 4.14.

how can i know the git branch and commit id of sgx-um binaries in tisdk-rootfs-image-dra7xx-evm_vsdk_3_4.tar.xz,

if i know the commit id, i can recompile it and then it can insmod successful.

best regards!

0 Ramprasad over 6 years ago in reply to fanok

TI__Mastermind 30480 points

Hi Fanok,

You should update your filesystem with 4.14 kernel image and kernel modules

Processors

Processors forum

Linux/TDA2EXEVM: port virtual drm to kernel 4.14