<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-xilinx.git/meta-xilinx-bsp/conf/machine/ultra96-zynqmp.conf, branch master</title>
<subtitle>Mirror of git.yoctoproject.org/meta-xilinx.git</subtitle>
<id>https://git.enea.com/cgit/linux/meta-xilinx.git/atom?h=master</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-xilinx.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/'/>
<updated>2022-07-28T19:45:08+00:00</updated>
<entry>
<title>meta-xilinx: Clean up vendor specific machine configuration files</title>
<updated>2022-07-28T19:45:08+00:00</updated>
<author>
<name>Sandeep Gundlupet Raju</name>
<email>sandeep.gundlupet-raju@xilinx.com</email>
</author>
<published>2022-05-06T00:50:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=4cd0ab00c97616b7a608f82c294176c153d94c43'/>
<id>urn:sha1:4cd0ab00c97616b7a608f82c294176c153d94c43</id>
<content type='text'>
1. Add new metal-xilinx-vendor layer which supports vendor specific
   machine configuration files, device-tree, kernel, platform-init etc.
2. Moved below vendor machine conf files, dt and related configs from
   meta-xilinx-bsp and meta-xilinx-contrib to meta-xilinx-vendor layer.
    - microzed-zynq7.conf
    - minized-zynq7.conf
    - picozed-zynq7.conf
    - zedboard-zynq7.conf
    - zybo-zynq7.conf
    - zybo-linux-bd-zynq7.conf
    - ultra96-zynqmp.conf
3. Obsolete qemu-zynq7, s3adsp1800-qemu-microblazeeb, v350-versal and
   vc-p-a2197-00-versal from meta-xilinx-bsp layer. Users should use
   zynq-generic.conf for zynq7000 qemu boot should be functionally
   equivalent to qemu-zynq7.
4. Add new MAINTAINERS.md file and move maintainers, Mailing list and
   Patches content from meta-xilinx-* README.md to MAINTAINERS.md file.
5. Updated README.md file for supported board machines files in
   meta-xilinx-bsp, meta-xilinx-contrib and meta-xilinx-vendor layers.
6. Disabled old drm kernel patches for zybo-linux-bd-zynq mahcine in
   meta-xilinx-contrib layer as these patches doesn't apply on 5.x
   kernel, if we don't hear from patch submitter we will remove these
   patches from meta-xilinx-contrib layer.
7. Removed drm kernel cache metadate for zybo-linux-bd-zynq7 machine
   as these configs are already available in xilinx_zynq_defconfig.
8. Fixed build issue for u-boot by changing
   PREFERRED_PROVIDER_virtual/bootloader from u-boot to u-boot-xlnx.
9. Add meta-xilinx-vendor to bblayers.conf.sample

Signed-off-by: Sandeep Gundlupet Raju &lt;sandeep.gundlupet-raju@xilinx.com&gt;
Signed-off-by: Mark Hatle &lt;mhatle@xilinx.com&gt;
</content>
</entry>
<entry>
<title>meta-xilinx-bsp: Covert ultra96-zynqmp and vck-sc-zynqmp from BOARD based</title>
<updated>2022-01-14T23:37:05+00:00</updated>
<author>
<name>Mark Hatle</name>
<email>mark.hatle@xilinx.com</email>
</author>
<published>2021-12-19T22:17:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=c55d616c997c36022b092a30e16f1b225482b8a1'/>
<id>urn:sha1:c55d616c997c36022b092a30e16f1b225482b8a1</id>
<content type='text'>
Use the MACHINEOVERRIDES to add the BOARD name so that overrides elsewhere
will work as expected.  Eventually the overrides will need to be adjusted.

Signed-off-by: Mark Hatle &lt;mark.hatle@xilinx.com&gt;
</content>
</entry>
<entry>
<title>meta-xilinx-bsp: Convert all BSPs to use the generic configs</title>
<updated>2022-01-14T23:37:05+00:00</updated>
<author>
<name>Mark Hatle</name>
<email>mark.hatle@xilinx.com</email>
</author>
<published>2021-12-19T17:40:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=ea7d0d351127bc8f0a902af7afe55bcdfc543714'/>
<id>urn:sha1:ea7d0d351127bc8f0a902af7afe55bcdfc543714</id>
<content type='text'>
Signed-off-by: Mark Hatle &lt;mark.hatle@xilinx.com&gt;
</content>
</entry>
<entry>
<title>Deprecate BOARD and BOARD_VARIANT support</title>
<updated>2022-01-14T23:37:05+00:00</updated>
<author>
<name>Mark Hatle</name>
<email>mark.hatle@xilinx.com</email>
</author>
<published>2021-12-18T21:44:31+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=4501eaa3c6eac161ec0aaec87d7b648361552912'/>
<id>urn:sha1:4501eaa3c6eac161ec0aaec87d7b648361552912</id>
<content type='text'>
If the BOARD and/or BOARD_VARIANT is set, continue to allow this to
work, however warn the user it is deprecated.

Signed-off-by: Mark Hatle &lt;mark.hatle@xilinx.com&gt;
</content>
</entry>
<entry>
<title>ultra96-zynqmp: Default to zynqmp eg variant</title>
<updated>2022-01-14T19:23:13+00:00</updated>
<author>
<name>Mark Hatle</name>
<email>mark.hatle@xilinx.com</email>
</author>
<published>2021-12-19T04:24:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=2ebe6ddbe38bb99154060aa56b56647f0b786f57'/>
<id>urn:sha1:2ebe6ddbe38bb99154060aa56b56647f0b786f57</id>
<content type='text'>
Signed-off-by: Mark Hatle &lt;mark.hatle@xilinx.com&gt;
</content>
</entry>
<entry>
<title>ultra96-zynqmp/zynqmp-generic: Specify the ultra96 so BOARD can select it</title>
<updated>2021-09-28T15:19:44+00:00</updated>
<author>
<name>Mark Hatle</name>
<email>mark.hatle@xilinx.com</email>
</author>
<published>2021-09-07T17:11:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=3de26cd3041552fc7852a266c6c020c5cf35b030'/>
<id>urn:sha1:3de26cd3041552fc7852a266c6c020c5cf35b030</id>
<content type='text'>
Move the ultra96-zynqmp.conf into the zynqmp-generic (via a require).  This
approach can be used for other board specific overrides if necessary.

Move MACHINE_FEATURES to the generic zynqmp-generic file, as that is requried
to make a superset.

Signed-off-by: Mark Hatle &lt;mark.hatle@xilinx.com&gt;
</content>
</entry>
<entry>
<title>u-boot-zynq-uenv: Remove incorrect dependency processing</title>
<updated>2021-09-28T15:19:43+00:00</updated>
<author>
<name>Mark Hatle</name>
<email>mark.hatle@xilinx.com</email>
</author>
<published>2021-08-30T17:32:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=75448876d3f68adba8d1d9c8c427a31eb9eeee36'/>
<id>urn:sha1:75448876d3f68adba8d1d9c8c427a31eb9eeee36</id>
<content type='text'>
An RDEPEND can not be turned into a DEPEND directly.  Indirectly the system
is capable of doing this via various mapping, but the function in use can
not do this safely.

Also move ultra96 firmware from RRECOMMEND to RDEPEND.

Signed-off-by: Mark Hatle &lt;mark.hatle@xilinx.com&gt;
</content>
</entry>
<entry>
<title>ultra96-zynqmp: Move to using zynqmp-generic as the foundation</title>
<updated>2021-09-28T15:19:43+00:00</updated>
<author>
<name>Mark Hatle</name>
<email>mark.hatle@xilinx.com</email>
</author>
<published>2021-08-30T17:40:23+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=039db5110bf98215bcdd7f3339de92aaf5a5b84d'/>
<id>urn:sha1:039db5110bf98215bcdd7f3339de92aaf5a5b84d</id>
<content type='text'>
We use zynqmp-generic (via a require) as the default now, and only set the
values that make the ultra96 unique.

Note, the two RRECOMMEND dependencies at the end.  These are requried for
WiFi and Bluetooth.

Signed-off-by: Mark Hatle &lt;mark.hatle@xilinx.com&gt;
</content>
</entry>
<entry>
<title>*.conf: use weaker assignment for UBOOT_MACHINE</title>
<updated>2021-07-14T21:57:15+00:00</updated>
<author>
<name>Raju Kumar Pothuraju</name>
<email>raju.kumar-pothuraju@xilinx.com</email>
</author>
<published>2021-04-28T12:31:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=a895ed95aba747bef685cfae691a44c564b50981'/>
<id>urn:sha1:a895ed95aba747bef685cfae691a44c564b50981</id>
<content type='text'>
Using weaker assingnment for UBOOT_MACHINE to update this value in
petalinux without _forcevariable.

Signed-off-by: Raju Kumar Pothuraju &lt;raju.kumar-pothuraju@xilinx.com&gt;
Signed-off-by: Sai Hari Chandana Kalluri &lt;chandana.kalluri@xilinx.com&gt;
</content>
</entry>
<entry>
<title>embeddedsw: Rework plm/pmu/psm firmware and Linux packaging</title>
<updated>2021-07-14T21:49:19+00:00</updated>
<author>
<name>Mark Hatle</name>
<email>mark.hatle@xilinx.com</email>
</author>
<published>2021-03-10T03:32:45+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-xilinx.git/commit/?id=453ba3b622e0dce7834209b453c01412028799fa'/>
<id>urn:sha1:453ba3b622e0dce7834209b453c01412028799fa</id>
<content type='text'>
In order to allow standalone (meta-xilinx-standalone), XSCT
(meta-xilinx-tools), and future items to work in the same way
the recipes have been restructured.

A *-firmware recipe will generate the firmware and stage it to do_deploy.
A *fw recipe will take the deployed version and package it for the Linux
side of things.  This allows the firmware generation to be easily extended
without requiring packaging knowledge.  Similarly packaging can be
extended for alternative boot/upgrade mechanisms as required.

In all cases, the MACHINE configuration will specify the default way
the components are to be built, along with the names of the item in
the deploy directory.

The PLM/PSM/PMU_IMAGE_NAME is the name for the generated firmware.

PLM/PSM/PMU_DEPLOY_DIR is the path to the constructed firmware.  This along
with the IMAGE_NAME above can be used to specify the location of an
externally generated set of firmware.

Addtionally the dependencies for building the plmfw/psmfw/pmufw can be
changed easily using PLM/PSM/PMU_DEPENDS and PLM/PSM/PMU_MCDEPENDS. The
former specifies dependencies in the same multiconfig, while the later
allows the component to require another multiconfig to have finihed.

The system has a referenced default, if multiconfig is enabled it will
automatically use it, otherwise it will try to use the recipe in the
main configuration.  (This will fail unless meta-xilinx-tools is available.)

Also two multiconfigs hve been implemented: versal-fw and zynqmp-pmufw
They can be enabled using BBMULITCONFIG += "zynqmp-pmufw" or versal-fw.

Signed-off-by: Mark Hatle &lt;mark.hatle@xilinx.com&gt;
</content>
</entry>
</feed>
