balaji-ch

Hi Raj, How did you create those GIFs ?

The DTS is as follows ``` memory@80000000 { device_type = "memory"; reg = ; }; reserved-memory { #address-cells = ; #size-cells = ; ranges; image_buf0: img_buf@0xbc000000 { compatible = "shared-dma-pool";...

Hey I am able to resolve it by ```dd if=/dev/udmabuf0 bs=1 count=1024 skip=0``` But when I use it like this ```dd if=/dev/mem bs=1 count=1024 skip=0 ``` or ```dd if=/dev/mem bs=1...

But here in this example https://github.com/ikwzm/ZynqMP-FPGA-Linux-Example-2-UltraZed/blob/master/negative.py udmabuf4.sync_for_device() udmabuf5.sync_for_device() is called in the for loop ?

So, even though it does not have any corresponding virtual address. Writing to vaddr will reflect in the /dev/mem for example ` vaddr[5000] = 42` will reflect in` 0x000000021bc00000+5000` ?

Thank you for your swift replies. AlsoI have one more question, In many examples thatI have seen, the size was always 1 page table. Can we use. 64 MiB for...

In many examples that mmap a physical memory I have seen the size was page_size in general. for instance here https://github.com/Digilent/Petalinux-Arty-Z7-20/blob/master/Arty-Z7-20/project-spec/meta-user/recipes-apps/peekpoke/files/peek.c ```c ptr=mmap(NULL,page_size,PROT_READ,MAP_SHARED,fd,(addr & ~(page_size-1))); ``` So, I was wondering...

refer this https://github.com/KhronosGroup/OpenVX-sample-impl/issues/14

Looking at your post **export OPENVX_DIR=$(pwd)/install/Linux/x32/Debug** I guess, you are trying a 32bit build. then the build command must be **python Build.py --os=Linux --venum --conf=Debug --conf_vision --enh_vision --conf_nn --arch=32** Read...

Delete everything and start afresh, following the build instructions carefully. unless you specifically want a 32 bit build , you don't need to specify arch=32 . And still you are...