From: "Otavio Salvador" <otavio.salvador@gmail.com>
To: meta-freescale@yoctoproject.org
Subject: Updates to meta-fsl-arm (master) in 2016-09-14
Date: Wed, 14 Sep 2016 11:16:32 -0300 [thread overview]
Message-ID: <57d95bc5.2e28c80a.a511.cc39@mx.google.com> (raw)
Hello,
I pushed following updates:
commit 9755c41ec02f671b5fed545db67f15b47fb4fdb4 (HEAD -> pending, yocto/master-next, yocto/master)
Author: Tom Hochstein <tom.hochstein@nxp.com>
Date: Tue Sep 13 19:53:19 2016 -0500
gstreamer1.0-plugins-imx: Fix inoperable package configuration
All packages were being built all the time because the configure
arguments from PACKAGECONFIG were not being passed. The problem
manifested itself as the QA issue build-deps, but the problem wasn't
fixed and the QA issue was silenced.
This is fixed by passing the PACKAGECONFIG arguments through EXTRA_OECONF.
Also, the build-deps QA issues are re-enabled.
Signed-off-by: Tom Hochstein <tom.hochstein@nxp.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
commit 8bbe70ada6a2278b59f06dd0dee783198afec182
Author: Daiane Angolini <daiane.angolini@nxp.com>
Date: Tue Sep 13 13:38:53 2016 -0300
firmware-imx: Install the firmware on a subfolders
The package provides firware files for 4 different modules.
This patch install each module in a different subfolder, so both can coexist.
Signed-off-by: Daiane Angolini <daiane.angolini@nxp.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
commit 1181e80a18393e1f2e477624b7724406ada9555f
Author: Marco Franchi <marco.franchi@nxp.com>
Date: Tue Sep 13 13:38:52 2016 -0300
firmware-imx: Fix the installation directory
The default Kernel defconfig points the bcm repository, but the recipes
was creating a brcm repository.
Signed-off-by: Marco Franchi <marco.franchi@nxp.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Regards,
--
Otavio Salvador O.S. Systems
http://www.ossystems.com.br http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750
reply other threads:[~2016-09-14 14:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=57d95bc5.2e28c80a.a511.cc39@mx.google.com \
--to=otavio.salvador@gmail.com \
--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.