All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@ossystems.com.br>
To: Chris Tapp <opensource@keylevel.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: Wandboard Quad experience (good!)
Date: Tue, 9 Jul 2013 18:51:06 -0300	[thread overview]
Message-ID: <CAP9ODKpHHyZo+qSbD-3hd10wNuC+EyPsyETibKpSOLoGYLp6eA@mail.gmail.com> (raw)
In-Reply-To: <81219393-2216-4F53-A236-30305D037889@keylevel.com>

On Tue, Jul 9, 2013 at 6:38 PM, Chris Tapp <opensource@keylevel.com> wrote:
> Thanks to help from Otavio and others, I now have an image building for the Wandboard Quad.
>
> I've built a custom OpenGLES application running under EGL (which I normally run on a Cedar Trail platform) and it's mostly running as expected - just need to work out why my gstreamer pipeline isn't working.
>
> The only bit that I had to work round was broadcom-nvram-config, which resulted in:
>
> NOTE: Resolving any missing task queue dependencies
> ERROR: Nothing RPROVIDES 'linux-firmware-INVALID' (but /media/SSD-RAID/meta-fsl-arm-extra-git/recipes-bsp/broadcom-nvram-config/broadcom-nvram-config.bb RDEPENDS on or otherwise requires it)
> NOTE: Runtime target 'linux-firmware-INVALID' is unbuildable, removing...
>
> I got round this by commenting out:
>
> MACHINE_EXTRA_RRECOMMENDS += " broadcom-nvram-config"

I fixed this and pused this for master-next; please confirm it works :-)

--
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://projetos.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750


  reply	other threads:[~2013-07-09 21:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-09 21:38 Wandboard Quad experience (good!) Chris Tapp
2013-07-09 21:51 ` Otavio Salvador [this message]
2013-07-09 22:03   ` Chris Tapp
2013-07-09 23:05     ` Chris Tapp
2013-07-10  2:57       ` John Weber
2013-07-10  7:50         ` Chris Tapp
2013-07-10 12:44           ` Otavio Salvador
2013-07-12 22:50         ` Chris Tapp
2013-07-13  0:07           ` John Weber
2013-07-13 21:26             ` Chris Tapp
2013-07-14 19:38               ` John Weber
2013-07-15  7:46                 ` Chris Tapp
2013-07-15 20:27                 ` Chris Tapp
2013-07-16  2:53                   ` John Weber
2013-07-16 15:58                     ` Thomas Senyk
2013-07-16 16:45                       ` Thomas Senyk

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=CAP9ODKpHHyZo+qSbD-3hd10wNuC+EyPsyETibKpSOLoGYLp6eA@mail.gmail.com \
    --to=otavio@ossystems.com.br \
    --cc=meta-freescale@yoctoproject.org \
    --cc=opensource@keylevel.com \
    /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.