All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Senyk <thomas.senyk@pelagicore.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: installing firmware-imx
Date: Tue, 05 Mar 2013 09:35:02 -0800 (PST)	[thread overview]
Message-ID: <2525222.0X1a7muAfm@rudolf> (raw)
In-Reply-To: <CAP9ODKpr1Vux++_1QpQF3EtH=0ySaqOzBejb-1NVRdoYZf47EQ@mail.gmail.com>

On Tue, March 05, 2013 13:57:51 Otavio Salvador wrote:
> On Tue, Mar 5, 2013 at 1:52 PM, Thomas Senyk
> 
> <thomas.senyk@pelagicore.com> wrote:
> > On Tue, March 05, 2013 13:38:00 Otavio Salvador wrote:
> >> On Tue, Mar 5, 2013 at 9:34 AM, Thomas Senyk
> >> 
> >> <thomas.senyk@pelagicore.com> wrote:
> >> > Hi,
> >> > 
> >> > I just tried to install the imx6 vpu firmware.
> >> > I needed to do:
> >> > IMAGE_INSTALL += "firmware-imx-vpu-imx6q"
> >> > 
> >> > firmware-imx-vpu or firmware-imx is not working.
> >> > .. that way my image is not only fsl-specific (which it already is due
> >> > to
> >> > fsl- codec) but also chip specific.
> >> > 
> >> > Not sure I get this right, but the fsl-codecs are useless without the
> >> > firmware, right?
> >> > If so: maybe the fsl-codecs/gst-fsl-plugin should have a RDEPENDS on
> >> > firmware- imx-vpu-<machine>?
> >> 
> >> Which image are you using? core-image-base and above ought to have the
> >> right set of firmware out of box.
> > 
> > Our own using 'inherit core-image'
> > So it's similar to (/more then) 'core-image-base'
> > 
> > I colleague found that adding packagegroup-base adds the firmware
> > 
> >  ... is that the right way of doing it?
> 
> Yes; this is the generic way of adding it. However it is automatically
> done by every image inheriting core-image. 

Ok, but then their is a bug :)
Our image does(!) 'inherit core-image' but the firmware does not get deployed.


> So you must be doing:
> 
> IMAGE_INSTALL = "... "
> 
> And this is wrong, in this specific case. Please change it to:
> 
> CORE_IMAGE_EXTRA_INSTALL += " ...  "


  reply	other threads:[~2013-03-05 17:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-05 12:34 installing firmware-imx Thomas Senyk
2013-03-05 16:38 ` Otavio Salvador
2013-03-05 16:52   ` Thomas Senyk
2013-03-05 16:57     ` Otavio Salvador
2013-03-05 17:35       ` Thomas Senyk [this message]
2013-03-05 17:36         ` Otavio Salvador
2013-03-05 17:58           ` 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=2525222.0X1a7muAfm@rudolf \
    --to=thomas.senyk@pelagicore.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.