Skip to content

weston-init: set require-outputs=none to allow startup without connected display#1880

Closed
yashgupta2126 wants to merge 1 commit intoqualcomm-linux:masterfrom
yashgupta2126:weston-init
Closed

weston-init: set require-outputs=none to allow startup without connected display#1880
yashgupta2126 wants to merge 1 commit intoqualcomm-linux:masterfrom
yashgupta2126:weston-init

Conversation

@yashgupta2126
Copy link
Copy Markdown

By default, Weston exits at startup if no output connector is reported as connected by the DRM subsystem. On platforms where displays are connected after boot via HPD (Hot Plug Detect), this causes the Weston service to be killed during early boot and remain down until manually restarted.

Setting require-outputs=none in the [core] section instructs Weston to start and remain running even when no connector is active at boot time. When a display is subsequently hot plugged and HPD is asserted, Weston automatically picks up the new connector and brings up the output without requiring a service restart.

…ted display

By default, Weston exits at startup if no output connector is reported
as connected by the DRM subsystem. On platforms where displays are
connected after boot via HPD (Hot Plug Detect), this causes the weston
service to be killed during early boot and remain down until manually
restarted.

Setting require-outputs=none in the [core] section instructs Weston to
start and remain running even when no connector is active at boot time.
When a display is subsequently hotplugged and HPD is asserted, Weston
automatically picks up the new connector and brings up the output without
requiring a service restart.

Signed-off-by: Yash Gupta <yash.gupta@oss.qualcomm.com>
@yashgupta2126
Copy link
Copy Markdown
Author

Hi @lumag , can you review this Pull Request ?

@lumag
Copy link
Copy Markdown
Contributor

lumag commented Apr 6, 2026

Hei @yashgupta2126 I am getting all notifications, no need to ping again.
This sounds like a generic change rather than something Qualcomm-specific. Please propose it to OE-core.

@ricardosalveti
Copy link
Copy Markdown
Contributor

Yeah, please propose to oe-core, this is not qcom specific. If not as default, at least have it in a way which we can set up a conditional in meta-qcom-distro to enable the behavior.

"

do_install:append:qcom() {
sed -i -e "/^\[core\]/a require-outputs=none" ${D}${sysconfdir}/xdg/weston/weston.ini
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This can introduce duplicates. The patch for oe-core, I assume, will not use sed.

@yashgupta2126
Copy link
Copy Markdown
Author

Raise change in OE-CORE layer, hence close this PR for meta-qcom

https://lists.openembedded.org/g/openembedded-core/message/235114

@quaresmajose
Copy link
Copy Markdown
Contributor

Merged upstream https://git.openembedded.org/openembedded-core/commit/?id=3d02dee3adfc6099358b41611904cdf88da0dcbe

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants