All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Philippe BALLEYDIER <PBalleydier@visionsystems.fr>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: What image should I build on the SabreLite?
Date: Thu, 06 Nov 2014 14:38:23 -0700	[thread overview]
Message-ID: <545BEA4F.8020509@boundarydevices.com> (raw)
In-Reply-To: <545BB9D9.3030102@boundarydevices.com>

Hi Philippe,

On 11/06/2014 11:11 AM, Eric Nelson wrote:
> Hi Philippe,
> 
> <snip>
> 
> While building from dizzy, I grabbed the latest 'fsl-machine-test'
> from O.S.Systems CI server (master branch):
> 
> 	http://ci.ossystems.com.br/public/fsl-community-bsp/master/389/x11/nitrogen6x/fsl-image-machine-test-nitrogen6x-20141102-389.rootfs.sdcard
> 
> This image has the same kernel version (g9f710da) as the head of
> dizzy, and it came right up.
> 
> 	root@nitrogen6x:~# cat /proc/version
> 	Linux version 3.10.17-1.0.1_ga+yocto+g9f710da (jenkins@builder) (gcc
> version 4.9.1 (GCC) ) #1 SMP Sun Nov 2 13:37:00 UTC 2014
> 	root@nitrogen6x:~# dmesg | grep ov5642
> 	mxc_v4l2_master_attach: ipu0:/csi0 parallel attached ov5642:mxc_v4l2_cap0
> 	ov5642 1-003d: created sysfs entry for reading regs
> 	camera ov5642 is found
> 
> I did see some weirdness in the mode setting of /dev/fb0, but the
> camera was functional, and I tested with a minimal gst-launch
> command-line:
> 
> 	root@nitrogen6x:~# gst-launch mfw_v4lsrc ! mfw_v4lsink
> 

I just tested fsl-image-multimedia-full on the dizzy branch and
things look the same there (including the weirdness surrounding
the display resolution).

The camera was recognized and gst-launch functioned properly.

Regards,


Eric



  reply	other threads:[~2014-11-06 21:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 11:11 What image should I build on the SabreLite? Philippe BALLEYDIER
2014-11-04 15:04 ` Eric Nelson
2014-11-04 15:16   ` Wally Yeh
2014-11-04 15:29     ` Otavio Salvador
2014-11-04 19:07       ` Daiane Angolini
2014-11-04 19:46         ` Otavio Salvador
2014-11-04 22:25           ` Wally Yeh
2014-11-04 18:50     ` Eric Nelson
2014-11-05  8:42   ` Philippe BALLEYDIER
2014-11-06  9:31     ` Philippe BALLEYDIER
2014-11-06 15:55       ` Eric Nelson
2014-11-06 18:11         ` Eric Nelson
2014-11-06 21:38           ` Eric Nelson [this message]
2014-11-07 10:00           ` Philippe BALLEYDIER
2014-11-07 13:55             ` Eric Nelson
2014-11-13 11:09               ` Philippe BALLEYDIER
2014-11-13 13:50                 ` Philippe BALLEYDIER
2014-11-06 21:47         ` 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=545BEA4F.8020509@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=PBalleydier@visionsystems.fr \
    --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.