| Age | Commit message (Collapse) | Author |
|---|
|
libmali-xlnx provides multiple shared libraries to support the update
alternatives mechanism. For this, shared libraries with different
backends are installed to the target and softlinked to libmali-xlnx.so.
When do_package task runs,
1. It creates a pkgdata/libmali-xlnx file that generates a list of
packages. In this case:
PACKAGES: libmali-xlnx-src libmali-xlnx-dbg libmali-xlnx-staticdev
libmali-xlnx-dev libmali-xlnx-doc libmali-xlnx-locale libmali-xlnx
libmali-xlnx-x11 libmali-xlnx-fbdev libmali-xlnx-wayland
libmali-xlnx-headless
2. It also tries to identify what are the shlibs files and creates a
pkgdata/shlibs2/libmali-xlnx.list file.
- The .list file contains a list of all shared object files
being provided by a package.
- This list is created by looking at list of packages from above
one by one.
- It creates a list of available .so files for target os and
then uses objdump -p to get more info(NEEDED and SONAME) about
the object files
- Writes to .list file with list of .so files and the paths
installed.
- This is generated by only looking at the .so files in each
package and not the defaiult backend being used in the recipe.
In Zeus, with this commit f7d46843e93f1acb4872bd5bcc12ed734de5168b on
package.bbclass, multiple shlib_providers for the same file error. Hence
when packages like cairo, qtbase build they error out with the following
error:
Multiple shlib providers for libMali.so.9: libmali-xlnx,
libmali-xlnx,libmali-xlnx, libmali-xlnx
Why this error generates for packages using libmali-xlnx:
When cairo/qtbase packages run do_package task, bitbake generates a
shlibs_provider_map list containing information (soname,ldir,ver) for
the given package using shlibs2/*.list files copied to pkgdata-sysroots.
libmali-xlnx.list contains list of all .so files installed inspite
default MALI_BACKEND_DEFAULT provider. Since the shlibs_provider_map
contains more than one provider, bitbake generates the above error and
fails.
To fix the above issue, append to the do_package task to update
the libmali-xlnx.list to specify only the MALI_BACKEND_DEFAULT provider
shlib and discard the remaining unused shlibs.
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
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>
|
|
Newlibs Makefiles use a variable CC_FOR_TARGET to build
libraries for the TARGET machine (as opposed to
CC_FOR_BUILD).
We pass CC on our compile function, which is normally
use to build, although in this case, the configure
script is trimming CC and using simply gcc for the target
machine, basically taking out the TUNE variables we pass
in CC as well, such as march, mfloat-abi and such.
This causes errors when building applications since
CC will try to use hard floating point for example
whereas the libc.a from newlib will contain libraries
built with the defaults which could be soft floating
point for example.
e.g.:
$ ${CC} a.c
real-ld: error: a.out uses VFP register arguments,
/usr/lib/libg.a(lib_a-stdio.o) does not.
Analizing the object files we can see that one of them
uses soft (library) and the other one uses hard
floating point (program):
$ readelf -A a.out | grep VFP
Tag_ABI_VFP_args: VFP registers
$ readelf -A usr/lib/libc.a | grep VFP
Hence why the linker complains.
Pass CC_FOR_TARGET with the contents of CC to override
the trimming from the configure script and build newlib
with the correct tune.
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
Signed-off-by: Alejandro Enedino Hernandez Samaniego <alejandr@xilinx.com>
|
|
Add sector size as 512K for larger SD, this is according to
specifications
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
This layer collects Yocto recipes required to build and run PYNQ based
examples using jupyter-notebooks on Zynq and ZU+ SoC's.
PYNQ is an open-source project from Xilinx that makes it easy to design
embedded systems with Zynq All Programmable Systems on Chips (APSoCs).
Using the Python language and libraries, designers can exploit the
benefits of programmable logic and microprocessors in Zynq to build more
capable and exciting embedded systems.
See https://github.com/Xilinx/PYNQ for more details and examples
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
Signed-off-by: Peter Ogden <ogden@xilinx.com>
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
|
Add qemu wiring to generic conf
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
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>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
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>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
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>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
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>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
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>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
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>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
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>
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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>
|
|
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 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>
|
|
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>
|
|
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>
|
|
Signed-off-by: Sai Hari Chandana Kalluri <chandana.kalluri@xilinx.com>
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>
|
|
Fix drm patch for v4.19 kernel, seems like the api
drm_mode_connector_update_edid_property to
drm_connector_update_edid_property in v4.19
Update the patch to make sure there are no build errors
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
|
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>
|
|
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>
|
|
Deploy u-boot.elf for Versal devices
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
|
This patch fixes the u-boot issue in do_install
| DEBUG: Executing shell function do_install
| install: cannot stat
'microzed_zynq7-poky-linux-gnueabi/u-boot/1_2019.01-r0/build/u-boot.elf':
No such file or directory
Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xilinx.com>
|
Sai Hari Chandana Kalluri
Swagath Gadde
Alejandro Enedino Hernandez Samaniego
Manjukumar Matha
Jaewon Lee
Mukund PVVN
Jeegar Patel
Madhurkiran Harikrishnan
Jean-Francois Dagenais
ch vamshi krishna
Min Ma
Mark Hatle