Make KMS drivers ignore bad EDID and force resolution.

Open
#5,368 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
c, linux

Research direction

The issue names no files, tests, or entry points. Start by tracing Raspberry Pi KMS handling of EDID and hotplugging and compare it with FKMS behavior; done means a display with bad EDID can be forced to 1920x1080 without cmdline additions while libcamera remains usable.

Written by the indexing model from the issue text.

Description

          @6by9 is there a way we can ask the Pi to not look for any EDID/hotplugging and just still connect it, so that we do not have to put any cmdline addition like that ? 

FKMS already works that way, it doesnt rely on EDID as you said. Would it be possible to do the same for KMS?

Originally posted by @rnayabed in https://github.com/raspberrypi/linux/issues/4719#issuecomment-974660353


I have a display with a wrong EDID file, I confirmed this. I want to run this display at 1920x1080 and it works great when the KMS driver is disabled. When the KMS driver is enabled only lower resolutions are available. I tried editing the cmdline.txt as suggested in the post above but no success.

The splash screens and loading screens are displayed at 1920x1080 all good there, but later on the resolution is limited. I need to run the KMS drivers because I am also using the libcam libraries which rely on the KMS drivers.

Is there a way to load the KMS drivers but ignore the EDID from the monitor? It works very well when KMS is disabled, but I need to enable KMS.

Dominant language
C
Stars
13.2k
Forks
5.5k
Avg merge
2d 21h
Merged PRs (30d)
21

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 raspberrypi/linux

All issues in raspberrypi/linux

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.