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>
* Add sgx to MACHINE_FEATURES to indicate that a particular machine supports
sgx.
* TI chips are available in multiple variants including some that supports sgx
while others do not.
* By adding sgx as a machine feature other layers can create generic
packagegroups or images for a particular soc but will only include sgx
dependencies if the particular machine has sgx support.
Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* Based on the EVM and beaglebone + NAND memory cape we can
increase the base file system size to 500MB since by default
there is about 504MB of space allocated to the file system
partition in the NAND.
* The max size in LEBs was determined using the formula at
http://processors.wiki.ti.com/index.php/UBIFS_Support
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* Add latest patches to linux-omapl138 that were added since this recipe was
added to meta-ti.
* Update to latest am180x-evm defconfig
* Mimic the following commits from arago:
linux-davinci: update to add mmc patches
* Optimizations to reduce overhead on weak platforms
linux: disable DMA for MUSB
* For the am3517, am180x, and am335x devices the CPPI 4.1 DMA
should NOT be used for the MUSB controller. Using this DMA
can cause the controller to lockup.
* Updated the defconfigs to set the use of PIO mode
* Added a patch to updated the PIO mode description to make it
easier to determine when it can be used.
Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* When testing on am37x-evm I noticed that no prompt to login was ever shown
when connected via serial port.
* I finally noticed that the SERIAL_CONSOLE variable was set incorrectly and
didn't match the value in the old Arago layer.
* After using the values specific in the machine file in the Arago layer I was
able to login via serial port.
* This has been verified on both the am37x-evm and am3517-evm.
Signed-off-by: Franklin S. Cooper Jr <fcooper@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Keystone uses the old ttyS0 serial name instead of the new ttyO0.
Also disable spawning gettys on virtual terminals.
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
* Updated the IMAGE_FSTYPES to ubi and tar.gz for the AMSDK
machine types as the base file system type.
* This was done to speed up compression/decompression time at
the expense of file size.
Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Also we need to pull in module-exa as xf86-video-omap relies
on it, at run time.
And replaced the default xorg.conf for 'omap4' machine to take
new driver into account. Do not enable HWcursor (e.g. mouse
using DSS overlay) to keep things simple for now..
Signed-off-by: Nicolas Dechesne <n-dechesne@ti.com>
Signed-off-by: Hervé Fache <h-fache@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Denys Dmytriyenko
Chase Maupin
Franklin S. Cooper Jr
Hao Zhang
Murali Karicheri
Cliff Brake
Nicolas Dechesne
Koen Kooi