You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As we're making changes to the TinyPilot EDID as part of the MacOS 13.3 issue, I'm realizing that it's pretty labor-intensive to inspect TinyPilot's EDID. We store it as a hex-encoded binary blob, but that means that changes to it are opaque until we import
We should add a step in CircleCI where we print out the decoded value of the EDID using edid-decode. To do this, we might have to store the EDID as its own file rather than as hex within the YAML. But we should have something in the CI logs that runs the EDID through edid-decode and prints it in the CI logs. That way, when we make EDID changes, it's easy to diff what's changed by comparing the current CI run to the CI logs in the main branch.
The text was updated successfully, but these errors were encountered:
As we're making changes to the TinyPilot EDID as part of the MacOS 13.3 issue, I'm realizing that it's pretty labor-intensive to inspect TinyPilot's EDID. We store it as a hex-encoded binary blob, but that means that changes to it are opaque until we import
We should add a step in CircleCI where we print out the decoded value of the EDID using
edid-decode
. To do this, we might have to store the EDID as its own file rather than as hex within the YAML. But we should have something in the CI logs that runs the EDID throughedid-decode
and prints it in the CI logs. That way, when we make EDID changes, it's easy to diff what's changed by comparing the current CI run to the CI logs in the main branch.The text was updated successfully, but these errors were encountered: