* Add sgx to the MACHINE_FEATURES so that the dra7xx-evm can
start including sgx libraries. NOTE: currently there are
no driver modules that work with v3.12 of the Linux kernel
but this does work with version 3.8.
Signed-off-by: Chase Maupin <Chase.Maupin@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>
Keystone II SOC family has multiple devices and EVMs: k2hk, k2l
and k2e, each EVM should have a separate machine config, and share
the common keystone SOC family.
Signed-off-by: Hao Zhang <hzhang@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
The new Texas Instruments Text File License (TI-TFL) is now replacing the
old Technology and Software Publicly Available (TSPA) license. But there are
older versions of the components previously released under TI-TSPA license.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Acked-by: Chase Maupin <chase.maupin@ti.com>
Acked-by: Franklin Cooper Jr. <fcooper@ti.com>
- The keystone-evm actually has 512 MB Nand
( Changing from previous size of 128 MB)
- LEB calculated with reserved 10 MB for boot and 20 MB
for receovery image
Signed-off-by: Sam Nelson <sam.nelson@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>
This reverts commit 35234fa937.
This was mainly needed for DTB fix that is specific to dylan branch and
is not required for master, plus it complicates life for other layers.
There is still a problem with Poky when manually adding layers and not
thinking about the correct order...
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
This helps avoid bblayers.conf ordering issues, when temporarily overriding
files from oe-core in meta-ti.
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>
While the code is being pulled from ti-u-boot integration tree, J6/DRA7xx bring up
is being done from a separate branch that does not include all the commits made
for am335x. Hence, until those branches are merged with the mainline and unified
in a single recipe, a separate recipe just for DRA7xx makes more sense. This
recipe should eventually go away and unified under u-boot-ti-staging one.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Acked-by: Chase Maupin <chase.maupin@ti.com>
* Updated the serial console to use ttyO0 which is what the
evm uses.
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* The U-Boot config to be used in the latest code has been updated
to use omap5_uevm instead of omap5_evm.
* Update to the latest code to pickup this change and modify the
machine file as well.
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* Add the dra7xx-evm machine type which is part of the omap-a15
SOC_FAMILY
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* Add the omap5-panda.dts file as a supported DTS to be built.
This file is for use on the panda and uEVM boards.
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* The serial console for the OMAP5 uEVM is ttyO2 not ttyO0
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* Add the machine configuration for the OMAP5 EVM device.
* Create the omap-a15.inc file to be shared with all OMAP
Cortex-A15 derivative devices.
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
SDKs or other users of meta-ti can still use one of the other recipes for
stability or featureset, by setting PREFERRED_PROVIDER in their config.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
SDKs or other users of meta-ti can still use one of the other recipes for
stability or featureset, by setting PREFERRED_PROVIDER in their config.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
SDKs or other users of meta-ti can still use one of the other recipes for
stability or featureset, by setting PREFERRED_PROVIDER in their config.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
SDKs or other users of meta-ti can still use one of the other recipes for
stability or featureset, by setting PREFERRED_PROVIDER in their config.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
SDKs or other users of meta-ti can still use one of the other recipes for
stability or featureset, by setting PREFERRED_PROVIDER in their config.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
SDKs or other users of meta-ti can still use one of the other recipes for
stability or featureset, by setting PREFERRED_PROVIDER in their config.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
SDKs or other users of meta-ti can still use one of the older 3.2 recipes for
stability or featureset, by setting PREFERRED_PROVIDER in distro or local config.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Acked-by: Chase Maupin <chase.maupin@ti.com>
* Update SRCREV for the recent merges in TI staging tree, still 3.8.2
* Bump MACHINE_KERNEL_PR to trigger rebuilding out-of-tree components
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* There is no support for these platforms from meta-ti.
* If someone is willing to maintain them, please let us know or feel free to
take it to a separate layer.
* Therefore, remove SoC and machine configs, kernel, u-boot and X11 configs
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
There is no support for this device from meta-ti. Plus I don't have the device.
If there's anyone willing to maintain it, please let me know or feel free to
take it to a separate layer.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
There is no support for this board from meta-ti. Plus I don't have the board.
If there's anyone willing to maintain it, please let me know.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Maupin, Chase
Hao Zhang
Denys Dmytriyenko
Sam Nelson
Franklin S. Cooper Jr