All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Carlos Rafael Giani <dv@pseudoterminal.org>,
	 meta-freescale@yoctoproject.org
Subject: Re: PXP test applications
Date: Sat, 11 Apr 2015 10:03:49 -0700	[thread overview]
Message-ID: <552953F5.30206@boundarydevices.com> (raw)
In-Reply-To: <55294C1C.5010502@pseudoterminal.org>

Hi Carlos,

On 04/11/2015 09:30 AM, Carlos Rafael Giani wrote:
> 
>> The "official repository" is the one inside the package....
>>
>> There is nothing more I can help, sorry. I also failed on getting it
>> to work.
>>
>> Daiane
>>
> 
> Which is a pity, because PxP seems to be partially broken in the kernel.
> That, or the headers contain a whole lot of formats that will be
> supported in the future, but aren't right now.
> A lot of source/destination format combinations produce erroneous
> content, just just plain black or green frames.
> 
> I attached the results of my findings. I did the tests with
> gstreamer-imx (current master) , Yocto Fido, kernel linux-imx
> 3.14.28-1.0.0_ga+g91cf351 , on a Sabre SD DualLite with integrated
> touchscreen. Plain framebuffer, no X, no Wayland.
> 
> The first matrix is the full version - I tried all formats with all
> formats. The second matrix is the one reduced to the subset that works
> best. Unfortunately, BGRx/RGB16 as source and UYVY as target format
> produce reversed colors, otherwise this would be a matrix with all
> combinations working. Also unfortunate is the fact that I420 didn't work
> at all as target format. Since the VPU expects I420 as input for
> encoding, PxP would have been useful as a single conversion step for
> some webcams that deliver Y42B data.
> 
> If anybody can make sense about why PxP is so broken, I'd be happy to
> hear about it.
> 

I can't comment on the state of the driver(s), but I can comment
on your tests and say "thanks"!

This e-mail should be bookmarked by anyone visiting the driver.

I hope we can test this out soon, but think it will have to wait
until we push forward to 3.14.28.

Regards,


Eric



      reply	other threads:[~2015-04-11 17:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-09 21:13 PXP test applications Eric Nelson
2015-04-10 12:09 ` 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 [this message]

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=552953F5.30206@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=dv@pseudoterminal.org \
    --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.