Could not compile stylesheet for simplistic. Using last compiled stylesheet.
Accepted Answer
0
Besides, I have managed to activate the HW accelerated resizer this way:
That high CPU load is because the pattern is still generated by a SW.
So it will scale the default test pattern 320x240 -> 800x400
export SINK="tidisplaysink2 device=/dev/video1 overlay-height=480 overlay-width=800 overlay-top=0 overlay-left=0" #fps 30, CPU 64% gst-launch videotestsrc ! dmaiperf print-arm-load=TRUE ! $SINK
That high CPU load is because the pattern is still generated by a SW.
So it will scale the default test pattern 320x240 -> 800x400
Responses (2)
-
Accepted Answer
0Hi justason,
Resizer it's inside ISP Module, you should use the isp infrastructure (that include CCDC, preview, resizer ...) and Resizer kernel module it's deprecated so this is why the Resizer inside DMAI framework it's not implemented.
Just see all /dev/videoX devices there using media-ctl you can configure it, in fact exist one (input) and the second (output) and you can use it directly ... if I rememeber correctly /dev/video6 and /dev/video7 should be the resizer ... you can configure it using media-ctl program ...
Manel -
Accepted Answer
0poky kernel has only /dev/video1 and /dev/video2 devices.
media-ctl -p -d /dev/video1
Opening media device /dev/video1
Enumerating entities
Found 0 entities
Enumerating pads and links
Device topology
media-ctl -p -d /dev/video2
Opening media device /dev/video2
Enumerating entities
Found 0 entities
Enumerating pads and links
Device topology
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »