Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

gauguin-q-oss tree does not compile

Open
#7 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
linux
Domain
embedded-iot, operating-systems

Research direction

Start with the gauguin-sm6350-overlay device-tree build and the duplicate qcom,mdss-dsi-bl-max-level errors reported for fragments 46 through 51. Review the proposed patch in device_tree_xiaomi_gauguin, then rebuild the dtbs target; the work is done when the overlay compiles without duplicate-property errors and the resulting device-tree image remains bootable.

Written by the indexing model from the issue text.

Description

From a basic setup using kernel e601e14 and device tree 726054c:

arch/arm64/boot/dts/vendor/qcom/gauguin-sm6350-overlay.dtbo: ERROR (duplicate_property_names): /fragment@46/__overlay__:qcom,mdss-dsi-bl-max-level: Duplicate property name
arch/arm64/boot/dts/vendor/qcom/gauguin-sm6350-overlay.dtbo: ERROR (duplicate_property_names): /fragment@47/__overlay__:qcom,mdss-dsi-bl-max-level: Duplicate property name
arch/arm64/boot/dts/vendor/qcom/gauguin-sm6350-overlay.dtbo: ERROR (duplicate_property_names): /fragment@48/__overlay__:qcom,mdss-dsi-bl-max-level: Duplicate property name
arch/arm64/boot/dts/vendor/qcom/gauguin-sm6350-overlay.dtbo: ERROR (duplicate_property_names): /fragment@49/__overlay__:qcom,mdss-dsi-bl-max-level: Duplicate property name
arch/arm64/boot/dts/vendor/qcom/gauguin-sm6350-overlay.dtbo: ERROR (duplicate_property_names): /fragment@50/__overlay__:qcom,mdss-dsi-bl-max-level: Duplicate property name
arch/arm64/boot/dts/vendor/qcom/gauguin-sm6350-overlay.dtbo: ERROR (duplicate_property_names): /fragment@51/__overlay__:qcom,mdss-dsi-bl-max-level: Duplicate property name
ERROR: Input tree has errors, aborting (use -f to force output)
make[4]: *** [scripts/Makefile.dtbo:25: arch/arm64/boot/dts/vendor/qcom/gauguin-sm6350-overlay.dtbo] Error 2
make[3]: *** [../scripts/Makefile.build:643: arch/arm64/boot/dts/vendor/qcom] Error 2
make[2]: *** [../scripts/Makefile.build:643: arch/arm64/boot/dts/vendor] Error 2
make[1]: *** [arch/arm64/Makefile:159: dtbs] Error 2
make: *** [Makefile:146: sub-make] Error 2

I've made a potential patch over at https://github.com/FloatingGhost/device_tree_xiaomi_gauguin which fixes compilation and allows a device to boot based on the dtb image, but i'm not well-versed enough in how the kernel works to know if this is the right way to go about it

Dominant language
No language data
Stars
136
Forks
65
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MiCode/kernel_devicetree

All issues in MiCode/kernel_devicetree

Similar issues

More Embedded & IoT issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.