All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Weber <rjohnweber@gmail.com>
To: Diego Sueiro <diego.sueiro@gmail.com>
Cc: "meta-freescale@yoctoproject.org"
	<meta-freescale@yoctoproject.org>,
	Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: Wandboard dual core-image-sato and qt4e-demo-image issues
Date: Tue, 23 Jul 2013 08:50:19 -0500	[thread overview]
Message-ID: <51EE8A1B.20000@gmail.com> (raw)
In-Reply-To: <CAMCfZKH=pMDPNm1W5eiypK2je27DsHcG=mRQRdohf+8w5id-DQ@mail.gmail.com>

I think so - I've tried to mix master and release branches and it does not work 
well, as they depend on each other.

Otavio has a really nice repo and setup script for this:
https://github.com/Freescale/fsl-community-bsp-platform


On 7/23/13 8:47 AM, Diego Sueiro wrote:
> Hi John,
>
> I did it after sent the e-mail. ;-)
> I need to add meta-openembedded too. I'm using both (meta-fsl-demos and
> meta-openembedded) on master branch, is it correct?
>
> Abraços,
>
> --
> *dS
> Diego Sueiro
>
> Administrador do Portal Embarcados
> www.embarcados.com.br <http://www.embarcados.com.br>
>
> Engenheiro de Controle e Automação
> UNIVERSIDADE FEDERAL DE ITAJUBÀ
>
> /*long live rock 'n roll*/
>
>
> On Tue, Jul 23, 2013 at 10:18 AM, John Weber <rjohnweber@gmail.com
> <mailto:rjohnweber@gmail.com>> wrote:
>
>     Diego -
>
>
>         It worked with "video=mxcfb0:dev=hdmi,__1440x900M@60,if=RGB24" on
>         core-image-sato
>         and core-image-x11.
>         But qt4e-demo-image doesn't. May a library is missing on roofts.
>
>         Let's see what's going to happen with a fsl-image-gui.
>
>
>
>     I noticed that your layers don't include meta-fsl-demos - that is the layer
>     that contains the fsl-image-(gui,test) recipes.  You'll want to pull that in
>     and integrate into your bblayers.
>
>     John
>
>


  reply	other threads:[~2013-07-23 13:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-23 13:12 Wandboard dual core-image-sato and qt4e-demo-image issues Diego Sueiro
2013-07-23 13:14 ` Otavio Salvador
2013-07-23 13:18 ` John Weber
2013-07-23 13:47   ` Diego Sueiro
2013-07-23 13:50     ` John Weber [this message]
2013-07-23 13:55       ` Diego Sueiro
2013-07-23 20:12         ` Diego Sueiro
2013-07-23 23:44           ` John Weber
2013-07-24 11:28             ` Diego Sueiro
  -- strict thread matches above, loose matches on Subject: below --
2013-07-22 14:29 Diego Sueiro
2013-07-22 16:46 ` Otavio Salvador
2013-07-22 16:55   ` John Weber
2013-07-22 16:58     ` Otavio Salvador
2013-07-22 18:35       ` Diego Sueiro
2013-07-23 11:23         ` Diego Sueiro
2013-07-23 12:14           ` Otavio Salvador
2013-07-23 12:17             ` Diego Sueiro
2013-07-23 12:26               ` Otavio Salvador

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=51EE8A1B.20000@gmail.com \
    --to=rjohnweber@gmail.com \
    --cc=diego.sueiro@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /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.