summaryrefslogtreecommitdiffstats
path: root/meta-xilinx-bsp
Commit message (Collapse)AuthorAgeFilesLines
...
* vck-sc-zynqmp: Machine configuration for vck190 system controllerSai Hari Chandana Kalluri2019-12-091-0/+39
| | | | | | | | | | | Add machine configuration vck-sc-zynqmp for vck190 system controller with required setting of board specific yocto variables needed for compilation of bootloader, kernel and device-tree. - linux-xlnx is the kernel provider - u-boot-xlnx is the u-boot provider Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* v350-versal.conf:Add versal board configurationMukund PVVN2019-12-091-0/+36
| | | | | | | | Add support to build images for v350-versal board configuration. V350 is a PCIe based card which has s80 Versal part. Signed-off-by: Mukund PVVN <mukundp@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* vc-p-a2197-00-versal.conf:Add versal Tenzing +SE1 board configurationManjukumar Matha2019-12-093-0/+175
| | | | | | | | | | | | | | | | | Add support to build images for vc-p-a2197-00-versal Tenzing board + SE1 board configuration vck190-versal.conf: Rename vc-e-a2197-00-versal to vck190-versal Rename vc-e-a2197-00-versal machine configuration to vck190-versal with required setting of board specific yocto variables needed for compilation of bootloader, kernel and device-tree. - linux-xlnx is the kernel provider - u-boot-xlnx is the u-boot provider Signed-off-by: Swagath Gadde <swagathg@xilinx.com> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* linux-xlnx.inc: Add MIPI kernel configuration for Ultra96Sai Hari Chandana Kalluri2019-12-093-0/+133
| | | | | | | Add MIPI kernel configuration for Ultra96 Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* ultra96-zynqmp.conf: Include mipi as MACHINE_FEATURESai Hari Chandana Kalluri2019-12-091-1/+1
| | | | | | | | | | Ultra96 provides support for MIPI Interface. To support the interface, additional kernel, device tree modifications are required and must be enabled only when mipi is included as MACHINE_FEATURE Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* linux-firmware_git.bbappend: Add hook for wl18xx and bts fileManjukumar Matha2019-12-092-1/+29
| | | | | | | | | Ultra96 board needs the wl8xx and bts file to enable wireless and bluetooth on the TI part. This recipe uses linux-firmware and modify to include only wl18xx binaries. We also depend on TIInit_11.8.32 bts, add an append to fetch the right bt firmware Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* ultra96-zynqmp.conf: Add support for Ultra96 evaluation boardManjukumar Matha2019-12-091-0/+42
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Ultra96™ is an Arm-based, Xilinx Zynq UltraScale+™ MPSoC development board based on the Linaro 96Boards specification. The 96Boards’ specifications are open and define a standard board layout for development platforms that can be used by software application, hardware device, kernel, and other system software developers. Ultra96 represents a unique position in the 96Boards community with a wide range of potential peripherals and acceleration engines in the programmable logic that is not available from other offerings More info: http://zedboard.org/product/ultra96 This patch adds machine configuration file for Ultra96 board with required setting of board specific yocto variables needed for compilation of bootloader, kernel and device-tree. - linux-xlnx is the kernel provider - u-boot-xlnx is the u-boot provider which will also generate SPL boot.bin While using SPL flow, you may need to provide additional hack to pass the PMU config object. This is similar to all ZU+ boards, due to gap in SPL flow unable to load PMU config object. Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* zcu216-zynqmp: Add support for zcu216 boardSwagath Gadde2019-12-091-0/+38
| | | | | | | | | | | Add machine configuration for zcu216 RFSoC board With required settings for board specific yocto variables needed for compilation of bootloader kernel and device tree -linux-xlnx is kernel provider -u-boot-xlnx is u-boot provider Signed-off-by: Swagath Gadde <swagathg@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* image-types-xilinx-qemu.bbclass: Add sector size as 512KManjukumar Matha2019-12-091-3/+3
| | | | | | | Add sector size as 512K for larger SD, this is according to specifications Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* machine-xilinx-default.inc: Adding required dependencies to image_wicJaewon Lee2019-12-091-0/+4
| | | | | | | | | | | | | | | | | Adding base required dependencies to do_image_wic[depends] to make sure the common files required to boot.bin have been deployed in DEPLOYDIR before the do_image_wic task tries to use them. zynqmp/versal will add virtual/kernel, virtual/boot-bin, virtual/bootloader, and virtual/arm-trusted-firmware zynq will add everything but virtual/arm-trusted-firmware If you want to add other files to IMAGE_BOOT_FILES, aside from files deployed from virtual/kernel, virtual/boot-bin, virtual/bootloader, you may need to manually add the dependency to do_image_wic[depends] Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* run-postinsts: Pass the output of the scripts run to kmsgAlejandro Enedino Hernandez Samaniego2019-12-091-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | The run-postinsts scripts are meant to run during the first boot of the device. At boot time, though, some resources are not available(e.g. STDOUT), hence why applications that run at this point need to be correctly daemonized, if, for some reason a script that runs is not able to start as a daemon, proper behavior cannot be guaranteed. For some unknown reason to me at this point, the console behaves differenly on our devices depending on the chosen boot mode, for example, when using sdboot, scripts that echo something during boot show the messages properly on the boot log, but when using jtag as boot mode, this does not happen and the messages are not shown. One of such cases happens with update-alternatives, which expects STDOUT to be present, and if it fails to get a possible output file descriptor it exits ungracefully, causing the run-postinsts script to exit itself. Pass the the kmsg character device as the output for the scripts run by the run-postinsts script, not only to be able to print out the output of such script to the boot log, but also to pass a valid file descriptor to the scripts so they behave properly. Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
* flashstrip utility: Build and ship flash strip utility needed for qemuJaewon Lee2019-12-092-0/+201
| | | | | | | | | | | | | | | | | | | Building and shipping flash strip utility needed for qemu: flash_strip flash_strip_bw flash_unstrip flash_unstrip_bw From the QEMU flash strip utilities wiki: QSPI Controllers implement byte/bit strip logic. Which mean's when an image is flashed, its stripped bit/byte wise into two flashes. User can use u-boot or Linux apps to flash the image after boot. By using flash strip utilities, we can flash the image without using u-boot. Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* bootgen_1.0.bb: Adding initial bootgen recipe to build bootgenJaewon Lee2019-12-091-0/+31
| | | | | | | | | | | | Building and installing bootgen, a tool that lets you stitch binary files together and generate device boot images. native and nativesdk classes are inherited as well to allow native version of bootgen to be built and to allow packaging of bootgen into an sdk if added into the dependency. Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* zynq-generic.conf: Add qemu wiring to generic confManjukumar Matha2019-12-091-0/+3
| | | | | | Add qemu wiring to generic conf Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* zcu1285-zynqmp.conf: Update UBOOT_MACHINEMukund PVVN2019-12-091-1/+1
| | | | | | | | | uboot config file is renamed from "xilinx_zynqmp_zc1275_revB_defconfig" to "xilinx_zynqmp_zcu1275_revB_defconfig", updated UBOOT_MACHINE to reflect the change Signed-off-by: Mukund PVVN <mukundp@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* zcu1275-zynqmp.conf: Rename zc1275 to zcu1275Mukund PVVN2019-12-091-4/+4
| | | | | | | | | zc1275 is renamed to zcu1275. All the references to zc1275 is renamed to zcu1275, this patch addresses machine conf name change and other references to zcu1275 Signed-off-by: Mukund PVVN <mukundp@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* machine-xilinx-default.inc: Add qemu-xilinx-helper-native as preferredManjukumar Matha2019-12-091-0/+3
| | | | | | | | | | | provider Python3 package from OE-core depends on qemu-helper-native, to meet this dependency use qemu-xilinx-helper-native as preferred provider. In addition this helps the sstate-cache to be similar across generic machines and evaluation boards. Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* zynq/zynqmp confs: Adding boot.scr to IMAGE_BOOT_FILESJaewon Lee2019-12-0910-0/+10
| | | | | | | | Adding boot.scr to IMAGE_BOOT_FILES so boot.scr is included in the wic sd card generation, if wic image generation is enabled Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* u-boot-zynq-scr: Setting sd as default bootmode for versalJaewon Lee2019-12-091-0/+4
| | | | | | | | | Setting sd as default bootmode for versal and adding default boot.scr for versal. NOTE: the difference between zynqmp and versal boot.scr template is versal doesn't have 'earlycon' Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* u-boot-zynq-scr: reworking boot.scr recipe to work for zynq and zynqmpJaewon Lee2019-12-0916-7/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | Separating out sample boot.cmd file for the three supported arch (zynq, zynqmp, versal), Updating devicetree, kernel, ramdisk load addresses for zynq, and dynamically setting DEVICE_TREE_NAME to either system.dtb or kernel dtb, depending on if dtg is used or not. This u-boot-zynq-scr implementation is put in to set the default boot and boot quicker than having to wait for the distro_bootcmd to cycle to the correct boot medium. For example, zynq arch has boot_targets set to "mmc mmc0 qspi usb0 pxe dhcp xilinx" and it takes about 30 seconds to try the 'xilinx' target which will run the correct bootargs. To use the boot.scr file, zynqmp boards must have BOOT.bin, Image, system.dtb, and boot.scr in the boot partition and a rootfs extracted in the second partition. Zynq boards must have BOOT.bin, uImage, system.dtb, boot.scr, and uramdisk.image.gz in the boot partition. (uramdisk.image.gz is the ${IMAGE}.cpio.gz.u-boot in deploy directory) Adding u-boot-zynq-scr dependency to all zynq and zynqmp machine confs. Conditionally adding system.dtb to IMAGE_BOOT_FILES for zcu102 to support boot.scr in qemu flow. Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* u-boot-zynq-scr: Add pxeboot support in u-boot-scrSwagath Gadde2019-12-091-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds pxeboot support for versal platform by adding default config file in pxelinux.cfg directory with below minimal mandatory information forbooting. label <name> - begin a label definition. labels continue until a command not recognized as a label command is seen, or EOF is reached. kernel <path> - if this label is chosen, use tftp to retrieve the kernel at <path>. it will be stored at the address indicated in the kernel_addr_r environment variable, and that address will be passed to bootm to boot this kernel. fdt <path> - if this label is chosen, it will load dtb at fdt_addr and that location of a fdt_addr will be passed to bootm when booting a kernel. Generally after u-boot bootup in jtag mode after autoboot time it scans usb and then ethernet and checks for pxelinux.cfg directory with default config file, if found it will load and boot linux. Steps to test: 1.acquire the board 2.in systest point the tftpd <path> 3.open serial terminal and connect com0 4.load the pdi from xsdb 5.stop at uboot promt and set serverip 6.dhcp 7.pxe get 8.pxe boot Signed-off-by: Swagath Gadde <swagathg@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* u-boot-xlnx_2019.2.bb: Rename zc1275 to zcu1275 board nameSai Hari Chandana Kalluri2019-12-091-2/+2
| | | | | | | | | | The zc1275-zynqmp board name is renamed to zcu1275-zynqmp. All references in u-boot repository have been modified to zcu1275 from zc1275. This patch updates the uboot platform init to use the zcu1275 name change Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* kernel-module-hdmi_git.bb: New Yocto recipe for Xilinx HDMI driversManjukumar Matha2019-12-091-0/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This recipe will pull in the Xilinx HDMI drivers and associated components, for soft IP, to be built as an out-of-tree modules. Following drivers will be pulled-in hdmi-rx (v4l2): The HDMI 1.4/2.0 Receiver Subsystem is a feature-rich soft IP incorporating all the necessary logic to properly interface with PHY layers and provide HDMI decoding functionality. The subsystem is a hierarchical IP that bundles a collection of HDMI RX-related IP sub-cores and outputs them as a single IP. The subsystem receives the captured TMDS data from the video PHY layer. It then extracts the video and audio streams from the HDMI stream and converts it to AXI video and audio streams. It includes support for HDCP 1.4 and 2.2 protocols hdmi-tx (drm): HDMI Tx subsystem is a feature-rich soft IP incorporating all the necessary logic to properly interface with xilinx PHY layers and provide HDMI encoding functionality. The subsystem is a hierarchical IP that bundles a collection of HDMI TX-related IP sub-cores and outputs them as a single IP. The subsystem takes incoming video and audio streams and transfers them to an HDMI stream. The stream is then forwarded to the video PHY layer. It includes support for HDCP 1.4 and 2.2 protocols video-phy (phy): Xilinx Video Phy implements the physical layer for enabling the plug-and-play connectivity with HDMI MAC transmit and receive subsystems. This driver is also used as the repository for common files used by hdmi rx and tx drivers including hdcp1.4 and hdcp2.2 software stack si5324 (ccf): Silicon labs clock generator driver specifically targeting the xilinx hdmi use-case. i.e. implemented only functionality required for xilinx hdmi soft IP at this time. dp159 (ccf): SNxDP159 device is a dual mode display port to TMDS retimer supporting DVI 1.0 and HDMI 1.4b and 2.0 output signals. When working as a retimer, the embedded clock data recovery cleans up the input high frequency and random jitter from video source. It also supports TMDS output amplitude adjust and output slew rate control. Signed-off-by: Rohit Consul <rohit.consul@xilinx.com> Signed-off-by: Shikhar Mishra <shikhar.mishra@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* kernel-module-vcu.bb : Autoload dmaproxy module on bootJeegar Patel2019-12-091-0/+2
| | | | | | | | dmaproxy module needs to be loaded after boot up. vcu omx il layer uses dmaproxy module for data transfer Signed-off-by: Jeegar Patel <jeegar.patel@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* kernel-module-mali: Upgrade the kernel space driver to r9p0Madhurkiran Harikrishnan2019-12-094-217/+4
| | | | | | | | | Upgrade the Mali-400 kernel space driver to r9p0. Key features: -Support linux kernel 4.19 -Added incremental features upgrade details for the DDk revision Signed-off-by: Madhurkiran Harikrishnan <madhurkiran.harikrishnan@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* kernel-module-mali: add patch to check dma_map_page errorJean-Francois Dagenais2019-12-092-0/+18
| | | | | | | | | | | | | | | | | | This fixes an error when using the module in a kernel configured with the CONFIG_DMA_API_DEBUG flag. utgard fd4b0000.gpu: DMA-API: device driver failed to check map error[device address=0x00000000325b0000] [size=4096 bytes] [mapped as page] ... [<ffffff80082f72bc>] check_unmap+0x44c/0x7e8 [<ffffff80082f76b8>] debug_dma_unmap_page+0x60/0x68 [<ffffff8000622e60>] mali_mem_os_alloc_pages+0x230/0x498 [mali] ... Acked-by: Hyun Kwon <hyun.kwon@xilinx.com> Signed-off-by: Jean-Francois Dagenais <jeff.dagenais@gmail.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* zocl_git.bb: Update the S path for zoclManjukumar Matha2019-12-091-1/+1
| | | | | | | | | | xrt repo has restructuring causing License of the zocl to break. ERROR: zocl-2.2.0+gitAUTOINC+f91777f3b8-r0 do_populate_lic: QA Issue: zocl: LIC_FILES_CHKSUM points to an invalid file: Update the S path for zocl to fix this issue Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* xrt_git.bb: Add icd support for edge platformsch vamshi krishna2019-12-091-0/+10
| | | | | | | | | | | The xilinx.icd file is required when user OpenCL application was compiled with "-lOpenCL". Without this fix, examples cases could not compile without Makefile change. Signed-off-by: ch vamshi krishna <chvamshi@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* xrt_git.bb: Fix xrt recipe for externalsrcManjukumar Matha2019-12-091-1/+1
| | | | | | | Having WORKDIR in LIC_FILES_CHKSUM will cause externalsrc to break. Change the LIC_FILES_CHKSUM to exclude the ${WORKDIR} Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* xrt_git.bb: update XRT dependencyMin Ma2019-12-091-1/+1
| | | | | | | Update XRT dependency to meet protobuf requirement Signed-off-by: Min Ma <min.ma@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* Update recipes for 2019.2 releaseJaewon Lee2019-12-0998-507/+2077
| | | | | | | | | | | Update u-boot, kernel, ATF, QEMU, pmu-firmware, multimedia recipes for 2019.2 release. The patch also upgrades gcc microblaze, newlib and libgloss versions. Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* libmali-xlnx: make version recognizableJean-Francois Dagenais2019-11-195-5/+5
| | | | | | | | | | | | | | Build systems (like meson), will look for >= of gbm pkg-config. "r8p0" makes these systems choke and fail to recognize gbm completely. The other .pc files next to gbm.pc suffer the same problem but have not caused me problems yet. 17.3 is a best minimal guess when comparing gbm.h relative to the one in mesa. Signed-off-by: Jean-Francois Dagenais <jeff.dagenais@gmail.com> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* libmali-xlnx: clean and fix FILESXTRAPATHSJean-Francois Dagenais2019-11-191-4/+1
| | | | | | | | | | | | | | Normally, when the colon ':' separator is on the right, the assignment is meant to be prepended to the variable. Using the _append override with both colon and spaces is an incoherent use of the FILESEXTRAPATH variable: https://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-FILESEXTRAPATHS Also removed the r9p0... path as it doesn't exist. Signed-off-by: Jean-Francois Dagenais <jeff.dagenais@gmail.com> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* libmali-xlnx: Upgrade the userspace driver to r9p0Madhurkiran Harikrishnan2019-11-196-8/+8
| | | | | | | | | | | | Upgrade the Mali-400 userspace driver to r9p0. Key features: -Minor bug fixes -Add user space support of GBM for MESA 17.3 -Supports Wayland > 1.15 Signed-off-by: Madhurkiran Harikrishnan <madhurkiran.harikrishnan@xilinx.com> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* libmali-xlnx: modify version on egl.pc for compatibilityAlejandro Enedino Hernandez Samaniego2019-11-191-1/+1
| | | | | | | | | | | Other packages may be using pkg-config to check for a compatible egl version. Align with the supported GL version to avoid errors when running configure for such packages. Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* libmali-xlnx: Change version on gbm.pc to be compatible with mesaAlejandro Enedino Hernandez Samaniego2019-11-191-1/+1
| | | | | | | | | | | Other packages may be using pkg-config to check for a compatible gbm version, which usually comes from mesa. Align with the supported mesa version to avoid errors when running configure for such packages. Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* libmali-xlnx: Dont provide KHR headersAlejandro Enedino Hernandez Samaniego2019-11-191-2/+0
| | | | | | | | | | | | | | Mesa-GL provides the KHR headers since 87c156183 (mesa) even if egl is not selected, assuming opengl is. This creates a conflict since when something DEPENDS on virtual/libgl and virtual/gles1, both dependencies will provide the same file. Dont provide KHR headers to avoid this conflict. Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* libmali-xlnx: Squash all monolithic library name into a variableMadhurkiran Harikrishnan2019-11-191-14/+15
| | | | | | | | Create a variable for monolithic library as it will be easy to call/make changes for future revision upgrade. Signed-off-by: Madhurkiran Harikrishnan <madhurkiran.harikrishnan@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* libmali-xlnx: fix x11 headersAlejandro Enedino Hernandez Samaniego2019-11-191-0/+3
| | | | | | | | | Since we cant rely on the fact that apps will use pkgconfig correctly we need to set the x11 headers accordingly (depending on DISTRO_FEATURES), e.g. qtbase, or libepoxy Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* libmali-xlnx: only use and install dependencies that the DISTRO supportsAlejandro Enedino Hernandez Samaniego2019-11-191-12/+43
| | | | | | | | | | | | | | | Be less strict with dependencies, if a user doesnt want a certain backend dont use or install dependencies for that backend. While switching alternatives at runtime would technically work, specifically speaking, the link to the selected alternative would be created correctly, the backend itself wouldnt necessarly work for obvious reasons, unless the user has the correct DISTRO_FEATURES enabled in their DISTRO configuration, which would pull all the necessary runtime dependencies for that backend. Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* libmali-xlnx: modify REQUIRED_DISTRO_FEATURESAlejandro Enedino Hernandez Samaniego2019-11-191-1/+1
| | | | | | | | | | | Use ANY_OF_DISTRO_FEATURES instead of REQUIRED_DISTRO_FEATURES to avoid pulling unnecessary dependencies for users. If a user wants to use a different backend, they should modify their own conf to add the required DISTRO_FEATURE. Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* libmali-xlnx.bb: ABIs are made consistent for all backendsMadhurkiran Harikrishnan2019-11-191-1/+0
| | | | | | | | Application binary interface are made consistent for all backends. GBM API support is now available for any libMali monolithic library. Signed-off-by: Madhurkiran Harikrishnan <madhurkiran.harikrishnan@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* libmali-xlnx: Use update-alternatives to switch between GL backendsAlejandro Enedino Hernandez Samaniego2019-11-191-34/+67
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | libmali provides GL backends based on x11, fbdev and wayland, we should be able to switch between them at runtime since it is the same ABI, it should only be a matter of loading the correct shared library by the interpreter (dynamic linker). Use the update-alternatives class, to provide a way for the user to choose the desired backend at runtime, do this by setting priorities, the package with the highest priority will be chosen as default at build time, but it can easily be changed at runtime afterwards. This change implies that the libmali package will install all backends regardless of which one was chosen, but it will only use one as default. Use the x11 backend by default at build time; given that it is the same ABI, applications which depend on libmali, can build regardless of the chosen backend at build time. Update-alternatives uses a set of commands on the postinst scripts when creating the root filesystem, which basically create the soft link between the chosen alternative and the binary/library. This usually works seamlessly (for binaries), but it does not in the case of libraries, because ldconfig is run at the end of the do_rootfs task, and it removes the link that was just created, it is important to note that this is simply normal ldconfig behavior and its not something we can fix, so we defer execution of update-alternatives until the first boot, hence avoiding the link removal by ldconfig. Switching backends at build time will also help to avoid longer build times, since it will only invalidate the do_package task, rebuilding an image after switching a backend (at build time) should only execute the do_package task along with the do_rootfs task. Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* libmali-xlnx: MALI will not provide wayland-eglMadhurkiran Harikrishnan2019-11-192-14/+0
| | | | | | | | | | Starting from 1.15 wayland, wayland-egl implementations are wired from wayland source code. EGL providers need not provide symbols/library. Applications will hence be linked to the one provided by the wayland. Signed-off-by: Madhurkiran Harikrishnan <madhurkiran.harikrishnan@xilinx.com> Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* libmali-xlnx: upgrade MALI recipe for 2019.2Manjukumar Matha2019-11-191-15/+8
| | | | | | | | | | | Upgrade MALI recipe and going forward from Wayland 1.15 the implementation for wayland-egl comes from wayland, EGL providers can leverage that and need not provide a separate implementation. Signed-off-by: Madhurkiran Harikrishnan <madhurkiran.harikrishnan@xilinx.com> Signed-off-by: Jaewon Lee <jaewon.lee@xilinx.com> Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* Add me to the maintainers listSai Hari Chandana Kalluri2019-11-191-0/+1
| | | | | Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com> Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* Add me to the maintainers listMark Hatle2019-11-181-0/+1
| | | | Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
* README.building: Update building instructions for multiconfig buildsAlejandro Enedino Hernandez Samaniego2019-08-161-18/+25
| | | | | | | Update building instructions for multiconfig builds Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* qemu-xilinx: split recipes for native (system, usermode) and targetAlejandro Enedino Hernandez Samaniego2019-08-167-11/+110
| | | | | | | | | | | | | | | | | The qemu recipe has been split in oe-core, into qemu target and qemu-native, to improve build performance (check 4852290). Previously it used BBCLASSEXTEND on the inc file (that we include) to create the nativesdk package. To keep up to date with OE-core, split out qemu-xilinx recipes as well, use a separate native inc file and create a recipe for qemu-xilinx-native and qemu-xilinx-system-native. This also requires us to update PREFERRED_PROVIDER for such recipes. Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
* machine-xilinx-default.inc: Deploy u-boot.elf for Versal devicesManjukumar Matha2019-08-161-0/+1
| | | | | | Deploy u-boot.elf for Versal devices Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>