templates: Add iq-x5121-evk device support#65
Conversation
Add base device configuration and meta-qcom project device file for iq-x5121-evk. The device uses flasher deployment with default gz compression for rootfs. The project device file includes flasher_device_type configuration to ensure proper device identification during flasher deployment. Signed-off-by: Shoudi Li <shoudil@qti.qualcomm.com>
Milosz Wasilewski (mwasilew)
left a comment
There was a problem hiding this comment.
We already have hamoa-iot-evk device in the LAB. It has iq-x7181-evk alias. I'm not very fluent in the SoC names. What is the upstream DTB file name for this board? Going forward we're going to use DTB file names for LAVA device types.
| @@ -0,0 +1,9 @@ | |||
| {% extends "devices/iq-x5121-evk" %} | |||
|
|
|||
| {# Device-specific test exclusions for meta-qcom project #} | |||
There was a problem hiding this comment.
could you split excluded tests into a separate commit with explanation why they're excluded?
|
|
||
| {% set flasher_device_type = "iq-x5121-evk" %} | ||
|
|
||
| {# Exclude unsupported testplan for this device #} |
There was a problem hiding this comment.
please split this into a separate patch with commit message explaining why it's excluded.
purwa-iot-evk.dtb |
|
thanks! |
|
We have qdl.jinja2 now. Could you migrate your templates to use it? I consider "flasher" to be obsolete now. |
Add base device configuration and meta-qcom project device file for iq-x5121-evk. The device uses flasher deployment with default gz compression for rootfs.
The project device file includes flasher_device_type configuration to ensure proper device identification during flasher deployment.