linux/meta-xilinx.git, branch scarthgapMirror of git.yoctoproject.org/meta-xilinx.githttps://git.enea.com/cgit/linux/meta-xilinx.git/atom?h=scarthgap2025-05-08T18:58:14+00:00meta-xilinx-mali400: xf86-video-armsoc: Only apply when libmali-xlnx is enabled2025-05-08T18:58:14+00:00Mark Hatlemark.hatle@amd.com2025-04-22T15:42:32+00:00urn:sha1:cd70c8d08de48963fe1a5d61d532a12b1d0730fc
The patches add acceleration optimizations to the build, but should only be
enabled if libmali-xlnx is going to be used. So switch based on DEPENDS,
and then adjust the DEPENDS to be switched based on the PREFERRED_PROVIDER
of virtual/libgles1.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
xf86-video-armsoc: Move mali400 changes from meta-xilinx-core to meta-xilinx-mali4002025-05-08T18:58:14+00:00Mark Hatlemark.hatle@amd.com2025-04-22T15:16:23+00:00urn:sha1:80923f7036d91b7c4ba20b19ca61f258b53295dc
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
zynqmp-common: Remove vcu machine feature2025-05-08T18:58:14+00:00Christian Kohnchris.kohn@amd.com2025-03-29T04:39:53+00:00urn:sha1:64e4f60397802c03727270dd8b6c6ae86a6dd4bb
Remove vcu machine feature from zynqmp-common machine as there is
no CG or DR device with a VCU.
Signed-off-by: Christian Kohn <chris.kohn@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
util-linux: carry the version from upsream master2025-05-08T18:58:14+00:00Trevor Woernertrevor.woerner@amd.com2025-03-28T17:10:57+00:00urn:sha1:87349a907b13bc5cabb9266acd64deb648e73ed2
wic uses the sfdisk(-native) utility from the util-linux project. Adding
support for 4k sectors requires a version of sfdisk that can handle
variable-sized sectors specified on the command-line. The version of sfdisk in
scarthgap (2.39.3) does not have this feature, but the version in master
(2.40.4) does.
Signed-off-by: Trevor Woerner <trevor.woerner@amd.com>
The microblaze util-linux patch needs to be updated for 2.40 as well.
Move existing integration to specifically target the Poky version,
while a new 2.40 version is created. This should allow either version
if the user decided to use PREFERRED_VERSION.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
wic: add support for sector size to sfdisk2025-05-08T18:58:14+00:00Trevor Woernertrevor.woerner@amd.com2025-03-28T17:10:58+00:00urn:sha1:a9b1c80db916102b08ff074fc16013c4e5b85734
Recent versions of the 'sfdisk' utility support non-512 byte sized sector
sizes by allowing the user to specify the size the wish to use on the command
line. Update wic to provide this option in the case where a user wishes to
generate an image with a sector size other than 512 bytes.
Signed-off-by: Trevor Woerner <trevor.woerner@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
wic: split out partition label from gpt name2025-05-08T18:58:14+00:00Trevor Woernertrevor.woerner@amd.com2025-03-28T17:10:56+00:00urn:sha1:02ef9a669d8c6d5d12b4c9b85384405c5aa1f1ca
A partition's label is stored as part of a partition's meta-data. Whether or
not labeling is supported depends on the filesystem type and whether or not
that type supports labels. GPT partition names, on the other hand, are stored
in the GPT table's metadata and only depends on whether or not GPT
partitioning is used; support for GPT partition names is not required
per-filesystem.
In a wks configuration file, the user specifies they want a filesystem label
applied to a filesystem by using the '--label <name>' directive. A user
specifies they want a GPT partition name applied to a partition using the
'--part-name <name>' directive.
The wic code conflates these two and sets a partition's GPT name in either
case when a user specifies '--part-name <name>' (correct) and '--label <name>'
(not correct).
Signed-off-by: Trevor Woerner <trevor.woerner@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
Remove 2022.X files, this work is now obsolete2025-05-08T18:58:14+00:00Mark Hatlemark.hatle@amd.com2025-03-30T22:28:20+00:00urn:sha1:dd14b068a23ddb2a5eb0bacd31f8ba0354d1cc79
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
device-tree: Fix device-tree include parsing2025-05-08T18:58:04+00:00Semyon Barenboymsemyon.barenboym@abra.co.il2025-02-11T07:11:32+00:00urn:sha1:ed2c91bd802f0c18ea1675594702f6f9ea509ca9
do_configure adds the EXTRA_DT_INCLUDES files to the DTS using the
`/include/` syntax, while Yocto's devicetree.bbclass runs the GCC
preprocessor over the resulting DTS file, leaving these include
statements untouched (since the GCC preprocessor only follows syntax
it recognizes).
This patch converts the include syntax to `#include`, ensuring that
the preprocessor processes it correctly, following and parsing all
included files. This allows a user DTSI to use nested `#include`
statements in overlays. e.g.:
system-user.dtsi
&axi_ad9083_rx_xcvr {
sys-clk-select =3D <XCVR_QPLL>;
out-clk-select =3D <XCVR_REFCLK_DIV2>;
};
Signed-off-by: Semyon Barenboym <semyon.barenboym@abra.co.il>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
meta-xilinx-mali400: kernel-module-mali: fix do_patch QA issue2025-03-30T20:29:05+00:00Quanyang Wangquanyang.wang@windriver.com2024-11-15T01:51:11+00:00urn:sha1:e02edbf88dbdc0432520c860b663896f00a5e120
Add "Upstream-Status" to the patches to fix do_patch QA issue.
Signed-off-by: Quanyang Wang <quanyang.wang@windriver.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
meta-xilinx: add Upstream-Status to the Xilinx patch2025-03-30T20:28:40+00:00Quanyang Wangquanyang.wang@windriver.com2024-11-15T01:51:12+00:00urn:sha1:199453d4eb6030084d55a126be06a9f9e436023c
This commit is to fix the building error:
ERROR: v4l-utils-1.28.1-r0.vr2400 do_patch: QA Issue: Missing Upstream-Status in patch
meta-xilinx/meta-xilinx-core/recipes-multimedia/v4l2apps/files/0001-v4l-utils-Add-support-for-new-media-bus-codes.patch
Please add according to https://docs.yoctoproject.org/contributor-guide/recipe-style-guide.html#patch-upstream-status . [patch-status]
Signed-off-by: Quanyang Wang <quanyang.wang@windriver.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>