-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Edid is invalid if x resolution >= 2304 #13
Comments
Trying to make a EDID for a Samsung Odyssey + VR HMD with
And have same error.
|
2304x1080 was the limit for 165mhz pixel clock. hmmm... |
limit of edid 1.3 spec: "Standard Timings shall not be used to define video timing modes with horizontal addressablepixel counts greater than 2288 pixels.In this case, the video timing mode shall be defined using the Detailed Timing Definition (Section 3.10.2) or the CVT Definition (Section 3.10.3.8)." From EDID 1.4 spec at https://glenwing.github.io/docs/VESA-EEDID-A2.pdf |
I am also seeing this problem with a DQHD 5120x1440p monitor.
|
On a 4K TV (LG):
Produced with the following mode line:
|
I have the same problem, trying to build edid for: Did you find a solution? |
No, unfortunately not. I'm living on 30Hz on this display - despite it being a recent card, AMD 6600 |
Same issue here for Dell 6k (6144x3456) monitor I tried to hand-patch a la:
However, this produces a 130 byte file (not a multiple of 128, which breaks the world) I'm also not sure the calculations would be correct anyway - I didn't look to see the actual instructions using those variables However, this may be on the right track if someone who also knows assembly and has the time to read the vesa/edid specs. From what I see in the comments, there are overflowed fields that are expected to be of a fixed length, and I'm not sure how to handle that ... Would be nice if this had been written in C |
Sounds like @newperson1746 has found the right spec and has described roughly what needs to be done from a logic perspective ... |
#5 may be having the same issue ... |
There is a patch to the edid generation that qemu implements here: https://gist.github.com/knazarov/40348fe805fce1fdaada11c863380109 That doesn't solve the problem with edid-generator, but ripping that out of qemu may be a better solution than trying to patch this project |
I met this error when I
make
with a modeline with resolution of2304x1296
.edid.S line 171 :
It seems that what happens is that when
XPIX
(x resolution) is >= 2304,(XPIX/8)-31
will be >=0x101
, which does not fit inside a byte.The text was updated successfully, but these errors were encountered: