Age | Commit message (Collapse) | Author |
|
The IMAGE_FSTYPES need to be overriden without using the SoC family
overrides, for user-friendness, and to allow this we need to use a SoC
variable to construct the default value for setting.
Related to [YOCTO: #8945].
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
As i.MX6UL has been changed out of mx6 SOC family, it need set UBOOT_ENTRYPOINT
Signed-off-by: Jun Zhu <junzhu@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The imx-gpu-viv-tools-dbg package where pointing to the very same
binary as imx-gpu-viv-tools, instead of the counterpart .debug
file. This removes this definition.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The defconfig changes should be done later in the process so the
.config file is generated, using any other mean, and mangled to
respect the distribution setting regarding the module use or not.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The 'swaprep.h' is an internal Xorg header and is not being installed
anymore. The swap features are provided by the 'misc.h' header now.
Fixes [YOCTO: #8737]
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The standard version does not use a Git repository so we should not
use Git to identify the commit of the build as it can end getting the
version from a wrong repository and can be misleading.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The patches applied on top of the source code are version specific and
should not be listed in the '.inc' file.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
There is no need to run 'make' in debug mode, by default, as it
increases log size and build time for no good reason.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Changes:
* vpu:
- Completely rewritten plugin code; elements now based on libimxvpuapi
instead of libfslvpuwrap
- imxvpuenc_h264 inserts SPS/PPS data in front of I/IDR frames
- imxvpuenc_mjpeg's quality factor actually has an effect, and is
equivalent to the libjpeg's quality factor (it is used in exactly the
same way to scale the quantization matrix' coefficients)
- the encoder's output buffers no longer have to use DMA memory; they
use regular system memory instead
- new support in imxvpudec (referred to as "chroma interleaving") for
NV12, NV16, NV24 as output formats as an alternative to the I420,
Y42B, Y444 formats
- removed all of the system frame number tracking code, since it is
unnecessary; Instead, the libimxvpuapi's context fields are used to
associate input/output frames with GstVideoCodecFrame system frame
numbers
- fix memory leaks related to missing buffer pool unref'ing
* imxv4l2videosrc:
- support for crop metadata
- element uses the width, height, etc. of the format that the device
actually uses during operation (instead of default values)
- autofocus control support via GstPhotography
- fix incorrect GLib warnings
- fix segmentation fault when shutting down the element
* eglvivsink:
- remove extra g_free() calls, which lead to runtime errors
- remove GLESv2 VIVANTE link dependencies
- add Android platform
- manually retrieve VIV direct texture functions
with this and the link dependency elimination, this means that for
platforms except the framebuffer one, no Vivante specific headers and
libraries are needed anymore
- fix blocking issue in the Wayland platform mainloop
* improved and expanded documentation
* pxp: NV16 *is* supported after all (it was actually a bug in GStreamer
pre-1.5.91)
NOTE: this does not break compatibility with GStreamer versions older
than 1.5.91
* compositor: Update backported aggregator code to GStreamer 1.6
* blitter:
- error handling improvements
- add missing buffer pool unref'ing, which lead to memory leaks
- add missing compositor dependency to blitter base
* uniaudio:
- only build the uniaudio plugin if at least one codec was found during
configuration
- disable plugin if the gstaudio library is not available
- add AAC profile field to the sink caps with GStreamer >= 1.4.4 to
ensure the uniaudio decoder is only used for AAC-LC data
* ipu: increase fill frame width from 8 to 64 pixels to make IPU fill
operations work with pre-3.14 Freescale kernels
* g2d: use padding pixels when setting surface parameters, fixing G2D
failures with frame sizes that aren't aligned
* wscript:
- improve Android support
- fix installation paths for the common, blitter, compositor libraries
Signed-off-by: Carlos Rafael Giani <dv@pseudoterminal.org>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Changes:
- add debian packaging files
- update waf to version 1.8.16
- add workaround in wscript to prevent stale pkg-config .pc files
- fix memory leak by adding missing IOFreeVirtMem() call in vpulib backend
Signed-off-by: Carlos Rafael Giani <dv@pseudoterminal.org>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The Tux logo should be disabled by default to allow a cleaner boot
process.
If a different configuration is needed of any specific machine, it can
be overriden using custom config.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Disable evbug, so machines using the kernel recipe do not have it
loaded by default.
The evbug kernel module can be enabled if needed, per machine, using a
custom config.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The SystemD requires the CONFIG_FHANDLE option to be enabled to
properly support the serial console getty initialization. This fixes
following error:
,----[ i.MX6Q SABRE Smart Device boot error ]
| [ TIME ] Timed out waiting for device dev-ttymxc0.device.
`----
The error has been catch while testing a customer image in a pure
SystemD distro, based on O.S. Systems Embedded Linux.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The module autoloading ensures 'galcore' to be probed as early as
possible during the boot. The order is important so the GPU can be
used as fast as possible, ensuring a reduced time until the initial
GPU-based application is loaded.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Signed-off-by: Chunrong Guo <B40290@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
This merges the 4.1.13 stable release fixes into the fork.
Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
This reverts commit 649f479f118567d62a5a57d690fb3fe3915f0ea7.
The 4.3 version of kernel cause build errors on lttng and cannot be
included until those are fix. We are reverting it now and will add it
back once OE-Core is fixed to support it.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Besides the revision change, this synchronizes the defconfig used for
the i.MX and the Vybrid SoCs. The only SoCs using a specific defconfig
file are the MXS-based ones (i.MX23 and i.MX28) as the others are
consolidated on the single defconfig file.
Change-Id: Id01a6050daaaee9bc931afa4583ec11f7b7d6da1
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
This includes following backported changes from 2016.01 development tree:
1b6aee7 mx7dsabresd: add secure boot support
54021ea imx: hab: add mx7 secure boot support
eea967b imx: hab: use read_fuse for secure boot settings
cca95ea arm: imx: add secure boot fuse details for imx7 SoC
5ef219e arm: imx: add secure boot fuse details for imx6 SoC
b2842cc imx: hab: add secure boot fuse details
31454f2 imx: hab: rework unified rom section for mx7
9ac3e4b imx: hab: use unified rom section for mx6sx and mx6ul
20235de imx: hab: rework secure boot support for imx6
8574461 imx: cpu: move common chip revision id's
a0c37ef imx: mx6sabresd: add i.MX6DQP Sabresd support
93bcc5f imx35, flea3: add FIT image support
10ca202 ts4800: add CONFIG_OF_LIBFDT
4198580 arm, imx6, aristainetos2: set gpr register after reset
e06ab75 arm, imx: add some gpr register defines
8af784c driver: misc: add MXC_OCOTP Kconfig entry
a022163 imx-common: timer: clean up code
Besides those, it also include:
4238786 cgtqmx6eval: Fix SPL support
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
imx-vpu is machine specific due to #define macros for the type of i.MX6
SoC (quad, duallite ..)
Signed-off-by: Carlos Rafael Giani <dv@pseudoterminal.org>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
This is a library for using the i.MX6 VPU. It is an alternative to
libfslvpuwrap, hosted on Github, and has an API that features several
improvements over libfslvpuwrap, which include:
* User-defined context information associated with input frames, which is
passed on to corresponding output frames (to be able to identify which
input frame produced which output frame)
* Groundwork for future DMA-BUF/BMM/ION/CMA allocator integration, using
file descriptors instead of physical addresses
* Indicators for when it is safe to try to decode frames, which is
critical in multi-threaded playback cases
* Simplified, higher-level JPEG en/decoding API, based on the VPU MJPEG
codec; useful for picture viewing without the extra boilerplate for
VPU-based en/decoding
Signed-off-by: Carlos Rafael Giani <dv@pseudoterminal.org>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Patch gst1.0-fsl-plugin's configure script to add a trailing space in the
FSL_MM_CORE_CFLAGS and FSL_MM_CORE_LIBS variables between different
pkg-config executions.
These variables are used later to pass parameters to the compiler and
as they are not built correctly, the 'configure' script fails to detect
some of the functionality:
Disabled features:
plugin: imxmp3enc
plugin: vpu_wrap
plugin: aiur
plugin: beep
This was working well in previous versions of Yocto, because pkg-config
until v0.28 was adding that trailing space:
http://cgit.freedesktop.org/pkg-config/commit/?id=f26a505826acec6b1e1af8d1efdf959913421c3a
but this is no longer true, so the trailing space has to be added in the
configure script.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The DirectFB project is dead upstream for a while and the backend is
deprecated so it is better to drop it and avoid new users to depend on
it and instead to focus in the current technologies for new projects.
This commit removes everything related to the DirectFB support so if
someone wish to revert it locally it can be easily done.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
Acked-by: Daiane Angolini <daiane.angolini@freescale.com>
|
|
This recipe is based on the now-deleted linux-imx-rt recipe, using the
same set of patches.
The linux-fslc-mx6 kernel is currently at upstream version 3.14.54, for
which no realtime patch has been released, but patch 3.14.51-rt52
applies cleanly.
Signed-off-by: Dominic Sacré <dominic.sacre@gmx.de>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
As we moved all the other MCC related recipes (mqxboot and
kernel-module-mcc), we should do so too with libmcc.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Fixed the following build errors with gcc5:
|error: linux/compiler-gcc5.h: No such file or directory
Signed-off-by: Chunrong Guo <B40290@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The 3.14.28 has not been fixed to work with the GCC 5.2 making it
unusable. Remove this version until someone does the upgrade to the
newer releases.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The 33615de (linux-imx: Upgrade to 3.14.38-6QP_beta release) did not
remove the linux-imx-mfgtool-3.14.28/mx6/defconfig file, keeping it
unused. Remove it now.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
This includes the Congatec QMX6 SPL support which is targetting
inclusion for U-Boot 2016.01 release. The following patches are
included:
23575d2 cgtqmx6eval: Add DFU support
112dfb1 iomux-v3: Take MX6D in consideration for imx_iomux_v3_setup_pad()
bf2ca16 cgtqmx6eval: Add SPL support
3bce451 cgtqmx6eval: Add fastboot support
77b786a cgtqmx6eval: Use SPI NOR to store the environment
f6bc396 cgtqmx6eval: Add SPI NOR flash support
540baa3 spi: Add SPI NOR protection mechanism
6e057b9 spi: sf_ops: Add SPI protection mechanism from the kernel
3f150e4 powerpc: Remove __ilog2_u64 and ffs4 from bitops
2feb00c compat: Remove is_power_of_2() definition
254550e nios2: Use the generic bitops headers
7611cdc nds32: Use the generic bitops headers
f9bfea4 openrisc: Use the generic bitops headers
d2f21eb sparc: Use the generic bitops headers
fde093e sandbox: Use the generic bitops headers
ef582a7 sh: bitops: Use the generic bitops headers
d068eae blackfin: bitops: Use the generic bitops headers
37d32df m68k: bitops: Use the generic bitops headers
902775c4 x86: bitops: Use the generic bitops headers
6ab6bf2 ARM: bitops: Use the generic bitops headers
8324309 include: Add generic bitops headers
5054c77 include: Add log2 header from the kernel
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The mqxboot and mcc Linux kernel module requires the Timesys kernel to
work. The kernel is not in use in meta-fsl-arm anymore and in long
term the Vybrid will be using the remoteproc mechanism to share
resources across the different CPU, inside of the SoC.
As consequence of the update for the Linux 4.1 kernel, those recipes
ought to move for meta-fsl-arm-extra where 3rd party boards can keep
using them.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Signed-off-by: Tzu-Jung Lee <roylee17@currantlabs.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Commit fa868c9e ("dts: imx6: fix sd card gpio polarity specified in
device tree") missed to be applied into 4.1.11 causing esdhc regressions
on mx6, so let's apply it so that we can have SD card working with
4.1.11.
Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The Vybrid reference board (twr-vf65gs10) now uses the linux-fslc
(4.1) kernel. This makes this kernel recipe unused. Remove it as it
has known security flaws, toolchain problems and is quite old.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Change the default Kernel to the linux-fslc 4.1 kernel.
What seems to work:
- UART
- CPU/Memory (obviously) and L2 Cache
- ARM global timer as clock source
- Pinctrl/GPIO support
- SD-Card
- USB Host (according to bootlog, not tested)
- SoC internal RTC (SNVS RTC)
- Watchdog
Not tested, but should be working:
- Audio using SGTL5000 connected via SAI (hardware not available)
- DCU Framebuffer device (hardware not available)
- Ethernet PHYs (not sure, might be a hardware issue)
Known to be missing:
- Spansion Flash S25FL128S connected via QuadSPI
- MCC v1 and v2
- Touchscreen with TWR-LCD-RGB (according to Tony)
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Add an optimized defconfig for Vybrid which includes NFC (NAND) and
DCU (fbdev) support for Vybrid.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
This updates linux-fslc to the latest version which includes
the Vybrid related patches.
622e3d4 video: fsl-dcu-fb: fix compile issue without PM_RUNTIME
b71a77f video: fsl-dcu-fb: fix pixel clock polarity
55a3f93 video: fsl-dcu-fb: add suspend/resume support
526c502 video: fsl-dcu-fb: fix signal polarity defines
3b5d7a3 ARM: dts: vf610-colibri: enable DCU framebuffer
0614d77 video: fsl-dcu-fb: support signal polarity configuration
202f53d video: fsl-dcu-fb: use native-display timing
1f632a8 video: fsl-dcu-fb: use num_timings to iterate timings
5801959 Documentation: DT: Add DCU framebuffer driver
5afe56f fb: Add DCU framebuffer driver for Vybrid VF610 platform
fdad0f6 ARM: clk: vf610: Add DCU and TCON clock support
0cdb0dc ARM: dts: vf610-twr: Enable DCU and TCON devices
ca0333a ARM: dts: vf610: Add DCU and TCON nodes
463b5a3 ARM: dts: vf-colibri: enable NAND flash controller
e439239 ARM: dts: vf610twr: add NAND flash controller peripherial
031328c mtd: nand: vf610_nfc: include missing pincrl/consumer.h
5812299 mtd: nand: vf610_nfc: add device tree bindings
48ea668 mtd: nand: vf610_nfc: add hardware BCH-ECC support
ce28974 mtd: nand: vf610_nfc: Freescale NFC for VF610, MPC5125 and others
4fc9a49 mtd: nand: add common DT init code
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
This merges the 4.1.11 stable release fixes into the fork.
Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
fixes:
| In file included from /home/a.mueller/tmp/oe-core-glibc/sysroots/zeravarimx6q/usr/include/EGL/eglplatform.h:38:0,
| from /home/a.mueller/tmp/oe-core-glibc/sysroots/zeravarimx6q/usr/include/EGL/egl.h:39,
| from ../src/modules/evas/engines/gl_common/evas_gl_api_ext.h:7,
| from ../src/modules/evas/engines/gl_common/evas_gl_core_private.h:5,
| from modules/evas/engines/gl_generic/evas_engine.c:2:
| /home/a.mueller/tmp/oe-core-glibc/sysroots/zeravarimx6q/usr/include/EGL/eglvivante.h:266:2: error: #error "Platform not recognized"
| #error "Platform not recognized"
| ^
Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com>
|
|
At first, this machine was supported only by u-boot-imx U-Boot provider, however
as soon as u-boot-fslc included this support, the U-Boot provider was changed.
During the change of default U-Boot provider, the SPL configuration end up being
missed.
The needed SPL configuration is set up in this patch.
Signed-off-by: Daiane Angolini <daiane.angolini@freescale.com>
Reviewed-by: Fabio Estevam <fabio.estevam@freescale.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
All Vybrid SoC's use the Cortex-A5 CPU. Add an appropriate default
tune for the vf SoC.
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
When the i.MX 6UltraLite (mx6ul) was separated from the SoC family mx6
(commit 24396b28f0137464cd82b9a19f705c1db180ead2) it started to create
invalid sdcard images.
This is because of SDCARD_GENERATION_COMMAND no more being triggered.
The solution in this moment is add a mx6ul override for the
SDCARD_GENERATION_COMMAND definition.
Signed-off-by: Felipe Provenzano <felipeprovenzano@maxtrack.com.br>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
This merges the v2015.10 final changes onto the FSLC fork, bringing
the fixes done on top of the rc5 release.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Those patch files were left orphan when upgrading the linux-imx and
u-boot-imx recipes, becoming unused. The removal of them cause no harm
and helps to keep the metadata clean.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Refers to the following commit of poky for more detail.
commit 722430a488f39bf583e4a557a254fb84fae4d0a7
Author: Darren Hart <dvhart@linux.intel.com>
Date: Wed Dec 12 14:39:15 2012 -0800
bootimg: Use FAT 32 for images larger than 512MB
Fixes [YOCTO #2138]
Signed-off-by: Tzu-Jung Lee <roylee17@currantlabs.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Update the U-Boot fork to a 2015.10-rc5 based version. This brings
several fixes for i.MX and Vybrid based systems. Mainly:
cf04ad3 arm: vf610twr: improve memory layout
d45fd01 colibri_vf: Fix bstlen field
e24bb2b mtd: nand: vf610_nfc: resync with upstream Linux version
f861f51 ls102xa: Fix reset hang
f532727 imx_watchdog: Add a header file for watchdog registers
040ef8f pcm052: fix MTD partitioning
61903b7 imximage: fix commands other than write_data
835c30e imximage: header.length of 4 is valid
Change-Id: Ifdb607d9a94ef594f3fe37d2b6388dc9a8268106
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
When generating the rootfs we need to include all the referenced
Device Tree files. The code were gracefully checking if the file
existed before building the image however the expected behavior is to
fail.
As consequence of this change, if someone is using a very old kernel
(no Device Tree based) and tries to generate an image, it will fail
until the machine definition is changed to not list Device Tree files
for installation.
Currently all machines supported by meta-fsl-arm BSP are consistent
for the default kernel in use however custom BSP may need to be
changed accordingly.
Change-Id: I548c65c61dfefe24154a455d097032b1598b14d3
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The code which copies the boot scripts and Device Tree files is
duplicated across the different image types. This patch reworks this
code to avoid this duplication.
Change-Id: Ib9405067a5419e1b295dfac9e3d3bd9b896d424e
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
Upstream Linux 4.1 supports the Vybrid SoC quite well, so enable
linux-fslc also for Vybrid SoC's.
Change-Id: I6745b67f4cc4b12ccc6f05754af9241e60731c6a
Signed-off-by: Stefan Agner <stefan.agner@toradex.com>
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The O.S. Systems Embedded Linux provides an alternative version of
U-Boot and, for completeness, an alternative recipe for
u-boot-mxsboot-native.
The provider, in imx-base.inc, had no default thus raising a
warning. This turns the u-boot-fslc-mxsboot-native as the default
provider but allows custom distributions to override it.
Change-Id: I46799f9ec744a074d95c383561cf0cbddb26e151
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|
|
The opencv 3.0 is not tested and does not have the i.MX6 specific
patch ported so we disable it for the i.MX6 SoC from Quad, DualLite,
SoloX and SoloLite families. The 2.4 is used instead.
This fixes following warning:
,----
| NOTE: multiple providers are available for runtime opencv-samples (opencv-samples, opencv)
| NOTE: consider defining a PREFERRED_PROVIDER entry to match opencv-samples
`----
Change-Id: I2f897cdd31dcee9046ee7d28ef4dcadb154ae88c
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
|