opencl-monitor does not distinguish between dra7xx and am57xx devices,
treating both as the same and attempting to build for am57xx regardless.
However, this is dependent on common-csl-ip-rtos, a component of PDK,
which in general does handle these devices differently. The definition
of am57xx SOCs in the PDK list from omap-15.conf gets inherited by
dra7xx-evm.conf, thereby creating a rule that all dra7xx PDK recipes
must build am57xx libraries. This results in a dra7xx image which is
much larger than necessary, and more severely, creates an artifical
dependency link between these two devices and introduces build failures
for various PDK recipes.
Instead, we now override the PDK SOC definition in dra7xx-evm.conf, and
only in the CSL RTOS recipe do we append the am57xx SOCS for dra7xx-evm
machine build. This allows for opencl-monitor to build successfully for
dra7xx while preventing any other PDK recipes from attempting to build
libraries for am57xx devices.
This is a workaround that must stay in place until opencl build can
properly comprehend am57xx and dra7xx independently, and/or omap-a15
is not implied to be synonymous with am57xx in various recipes.
Signed-off-by: Stephen Molfetta <sjmolfetta@ti.com>
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* The omapl137 family does not have linux support and is only
supported by baremetal and TI RTOS.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* The c66x SOCs (e.g. c665x-evm and c667x-evm) are DSP-only devices,
and therefore do not have a supported kernel nor an integrated
toolchain.
* Add these machines to allow the creation of baremetal and TI RTOS
packages.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* Set the ti-pdk class variables which sets the list of devices and
boards supported.
Signed-off-by: Jacob Stiffler <j-stiffler@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The bb.data.getVar() API has been deprecated & removed. This change
follows that change and allows MACHINE=beaglebone to work again.
Signed-off-by: Gary Thomas <gary@mlbassoc.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
AM43x was missing the hdmi dtb file in the
KERNEL_DEVICETREE variable. Adding this in allows for
a copy to deploy directory.
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Set DEFAULTTUNE optimization in BSP from specific Cortex level to more generic
armv7a, but keep thumb, neon and hard-float options enabled due to numerous BSP
components requiring them. While enabling additional Cortex optimization might
gain a tiny performance improvement, it makes binary feeds incompatible between
A8, A9 and A15 machines, leads to unnecessary rebuilds and hides potential
packaging or recipe issues. Hence the decision to enable Cortex optimization
should be left to the Distro.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Correct the name of the variable used to define the size of the logo:
GUI_MACHINE_CLASS renamed MACHINE_GUI_CLASS.
Signed-off-by: Thomas Perrot <thomas.perrot@tupi.fr>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* Enable "sgx" feature on all - the driver may still be missing, but GLES is
available from omap5-sgx-ddk-linux package
* Enable "touchscreen" feature only on dra7 and am57 - not available on omap5
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Acked-by: Franklin Cooper Jr. <fcooper@ti.com>
* Create the dra7xx.inc file which inherits the omap-a15.inc file
and then adds the dra7xx as another valid SOC_FAMILY setting.
* The addition of the dra7xx SOC_FAMILY is done while still keeping
access to the omap-a15 family. What this means is that omap-a15
can apply to omap5-evm, dra7xx-evm, and am57xx-evm. Then the
dra7xx family can be used to differentiate between omap5 and
dra7xx based devices.
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Acked-by: Franklin Cooper Jr. <fcooper@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
k2l-evm machine config shares the same Keystone SoC family, it has K2L EVM
specific machine configuration for UBI image, boot monitor, U-boot, etc.
Signed-off-by: Hao Zhang <hzhang@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* Remove the RDEPENDS for the am33x-cm3-initscript package since
the latest kernel source use the hotplug functionality to load
the firmware.
* Updated the SRCREV to the latest kernel sources which include
the hotplug fix.
* Bump the MACHINE_KERNEL_PR for the am335x and am437x devices
which are affected.
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* By setting the UBI_VOLNAME variable the default name for the
UBI rootfs will match the default used by u-boot so images
built through OpenEmbedded will work with out-of-box u-boot.
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* The VPE firmware should only be added for the dra7xx-evm
machine type since that is the device with the VPE IP.
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* New Graphics SDK with am43x support has been added.
Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* Now the DRA7xx support is fully merged into upstream u-boot
then we can remove setting the PREFERRED_PROVIDER for
u-boot and virtual/bootloader to u-boot-dra7xx and instead
pick up the default setting from the omap-a15.inc file.
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* For am335x and am437x, the kernel and u-boot expects the ubifs volume name
to be set to "rootfs".
* Set UBI_VOLNAME variable to "rootfs" so that the ubifs files generated by OE
will work.
Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
To be used with latest u-boot that prefers zImage over uImage
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Acked-by: Chase Maupin <chase.maupin@ti.com>
* To be used with latest u-boot, that prefers zImage over uImage
* ti33x will follow as soon as u-boot changes its default for that platform
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Cc: Tom Rini <trini@ti.com>