Merge ~canonical-kernel-team/+git/autotest-client-tests:phlin/fix-j-ubuntu_xilinx into ~canonical-kernel-team/+git/autotest-client-tests:master

Proposed by Po-Hsu Lin
Status: Merged
Merged at revision: b6ff29c526f66aa35ca78f7cff5e7c9c73e22fa4
Proposed branch: ~canonical-kernel-team/+git/autotest-client-tests:phlin/fix-j-ubuntu_xilinx
Merge into: ~canonical-kernel-team/+git/autotest-client-tests:master
Diff against target: 29 lines (+6/-1)
2 files modified
ubuntu_xilinx/lib/run-test (+1/-1)
ubuntu_xilinx/ubuntu_xilinx.py (+5/-0)
Reviewer Review Type Date Requested Status
Francis Ginther Approve
Jesse Sung Pending
Review via email: mp+443543@code.launchpad.net

Commit message

On the re-provisioned KV260 with Jammy Xilinx kernel, this test will
complain about:
 1. Missing xlnx-config command, this can be fix by installing the
    xlnx-config snap. I guess we don't have this issue on F-xilinx
    because this snap has already been included in the image.
 2. Mismatched name in /proc/device-tree/compatible, we are looking
    for 'k26' here, it works for Focal but not Jammy. We will need
    'kv26' here for Jammy
    $ cat /proc/device-tree/compatible
    xlnx,zynqmp-sk-kv260-rev1xlnx,zynqmp-sk-kv260-revBxlnx,zynqmp-sk-kv260xlnx,zynqmp

To post a comment you must log in.
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

We might need to figure out why it's k26 on Focal, kv26 seems more reasonable to me.

Revision history for this message
Francis Ginther (fginther) wrote :

Changes look fine. I agree it would be good to understand the difference in `/proc/device-tree/compatible`. Is this a different kernel with a different device tree?

review: Approve
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Here is the output from F-xilinx on KV260:
$ cat /proc/device-tree/compatible
xlnx,zynqmp-smk-k26-rev1xlnx,zynqmp-smk-k26-revBxlnx,zynqmp-smk-k26-revAxlnx,zynqmp-smk-k26xlnx,zynqmp

From what I can found on the Internet, KV260 is "a vision application development platform for Kria K26 SOMs (system-on-module)".
I will get this merged now and open a bug to track this /proc/device-tree/compatible difference, make sure it is expected.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1diff --git a/ubuntu_xilinx/lib/run-test b/ubuntu_xilinx/lib/run-test
2index 652e6ef..89dd4d3 100755
3--- a/ubuntu_xilinx/lib/run-test
4+++ b/ubuntu_xilinx/lib/run-test
5@@ -115,7 +115,7 @@ function _set_globals()
6 tr -d '\0\n')
7
8 # Find the board
9- if [ $(cat /proc/device-tree/compatible | grep -ao k26 | head -1) ] ; then
10+ if [ $(cat /proc/device-tree/compatible | grep -ao -e k26 -e kv26 | head -1) ] ; then
11 RT_XILINX_BOARD="kv260"
12 fi
13
14diff --git a/ubuntu_xilinx/ubuntu_xilinx.py b/ubuntu_xilinx/ubuntu_xilinx.py
15index af14a86..f362792 100644
16--- a/ubuntu_xilinx/ubuntu_xilinx.py
17+++ b/ubuntu_xilinx/ubuntu_xilinx.py
18@@ -7,6 +7,11 @@ class ubuntu_xilinx(test.test):
19 def initialize(self):
20 pass
21
22+ def setup(self):
23+ snap_pkgs = ['xlnx-config']
24+ cmd = 'snap install --classic ' + ' '.join(snap_pkgs)
25+ utils.system_output(cmd, retain_output=True)
26+
27 def run_once(self, test_name):
28 cmd = os.path.join(self.bindir, 'tests', test_name)
29 utils.system_output(cmd, retain_output=True)

Subscribers

People subscribed via source and target branches

to all changes: