From: Eric Nelson <eric.nelson@boundarydevices.com>
To: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: PXP test applications
Date: Thu, 09 Apr 2015 14:13:40 -0700 [thread overview]
Message-ID: <5526EB84.8070302@boundarydevices.com> (raw)
Hi all,
Does anyone know how to run the pxp_test.out program
from /unit_tests?
I can run it, but it's not clear what is supposed to happen.
root@nitrogen6x:/unit_tests# ./pxp_test.out -H
Usage: ./pxp_test.out -I "<options for each instance>" -H display this help
options for each instance
-o <output file> Write output to file
If no output is specified, default is panel
-r <rotation angle>
-h <horizontal flip>
-v <vertical flip>
-l <left position for display>
-t <top position for display>
-i <pixel inversion>
I can run it, but I'm not sure what it's supposed to do.
root@nitrogen6x:/unit_tests# ./pxp_test.out -I "-h -v -l 10 -t 100 -i
akiyo.mp4"
pxp_test.c:358 opening this fb_dev - /dev/fb0
pxp_test.c:358 opening this fb_dev - /dev/fb1
pxp_test.c:358 opening this fb_dev - /dev/fb2
pxp_test.c:358 opening this fb_dev - /dev/fb3
pxp_test.c:361 Unable to open /dev/fb3
root@nitrogen6x:/unit_tests# echo $?
0
Carlos pointed out that we had been missing a bit
from our SDL device trees:
https://github.com/boundarydevices/linux-imx6/commit/5be9587
And I was hoping to actually exercise the driver and
am lost about where to start.
The imxpxpvideosink seems to lock up with a message of:
pxp_dispatch_thread: task is timeout
Regards,
Eric
next reply other threads:[~2015-04-09 21:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 21:13 Eric Nelson [this message]
2015-04-10 12:09 ` PXP test applications Daiane Angolini
2015-04-10 14:47 ` Eric Nelson
2015-04-10 15:58 ` Daiane Angolini
2015-04-10 18:32 ` Eric Nelson
2015-04-11 14:28 ` Daiane Angolini
2015-04-11 16:30 ` Carlos Rafael Giani
2015-04-11 17:03 ` Eric Nelson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5526EB84.8070302@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=meta-freescale@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.