diff options
| author | Mark Hatle <mark.hatle@amd.com> | 2024-06-03 08:45:59 -0600 |
|---|---|---|
| committer | Mark Hatle <mark.hatle@amd.com> | 2024-06-12 15:30:58 -0600 |
| commit | fff9b1d009c2a86d5cdadd1dd8832fd4e471de27 (patch) | |
| tree | 2e22f2e1998b191e589dd42bd689aca4982c1dad /meta-xilinx-core/recipes-devtools/qemu/qemu-8.1/0002-python-qemu-rename-command-to-cmd.patch | |
| parent | 70c306a03620cd11ddbb75746cabb00768b1a149 (diff) | |
| download | meta-xilinx-fff9b1d009c2a86d5cdadd1dd8832fd4e471de27.tar.gz | |
zynqmp-generic.conf: Fix qemu pmu firmware path
The path specified is the internal firmware path. This could be in a the
current deploy directory, a multiconfig deploy directory or some other place
directly specified by the user.
When using the sstate-cache, the build of the component in the a multiconfig
directory can be skipped, causing an error to find the component.
Instead we want to use OUR deploy directory, which will always have a copy
of the pmu firmware, no matter how it was constructed or packaged.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
(cherry picked from commit f381c7871b973e131aad57113b1c4fb1a3999432)
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
Diffstat (limited to 'meta-xilinx-core/recipes-devtools/qemu/qemu-8.1/0002-python-qemu-rename-command-to-cmd.patch')
0 files changed, 0 insertions, 0 deletions