Skip to content
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

ddcctl submodule #71

Open
wants to merge 14 commits into
base: master
Choose a base branch
from
Open

ddcctl submodule #71

wants to merge 14 commits into from

Conversation

Kalvin126
Copy link
Contributor

@Kalvin126 Kalvin126 commented Mar 7, 2017

Hey @superduper and all watching this repo,

Not sure how I did not notice my fork got pulled into this base long ago. I have been busy with post-college iOS work. I finally got around to integrating ddcctl and including it as a submodule to use @kfix's version of DDC. Awkward enough, I see @wagenet has already gotten this done albeit not using submodules.

I also think we should get rid of the compatibility chart. I do not know why I thought that was a good idea. Multiple people making PRs to update the README is a mess. Replacing the old ddc core with kfix's would also warrant a reset on the table.

@francosolerio
Copy link

New DDC breaks compatibility with LG 5K Ultrafine display / MacBook Pro 15 Touchbar.

@Kalvin126
Copy link
Contributor Author

Kalvin126 commented Mar 7, 2017

So you are not able to use superduper's build?
DDC compatibility is such an issue on Macs I feel. The tool, with the old CGDisplayIOServicePort with macOS 10.11 worked for my Dell U2515h and P2014h but after going to 10.12, it stopped working. With the new method to get the service port, only my U2515h works now ._.

Perhaps it should revert to CGDisplayIOServicePort if read/writes fail.

@francosolerio
Copy link

francosolerio commented Mar 7, 2017

Exactly. Superduper current commit (f16fd62) doesn't work. Older commit (781dde7) works perfectly.

@kfix
Copy link

kfix commented Mar 7, 2017

I'm fine with ddcctl being vendored via submodule if actual debugging is done for incompatibility reports.

I'm not fine with "it doesn't work, please fix" complaints with absolutely no debug work done by the reporter.
I can't test & debug hardware I don't have. I focus on the HW I have (access to) and that's what ddcctl/master branch reflects.
If BrightnessMenulet vendors ddcctl, I will definitely turn disable GitHub Issues tab and only accept PRs.

@Kalvin126 if you revert to CGDisplayIOServicePort people will complain about compiler warnings and they will really complain when it is removed from CoreGraphics.

@Kalvin126
Copy link
Contributor Author

Kalvin126 commented Mar 7, 2017

I understand. In my diff, you'll see I removed the chart and feedback chart.
On a side note, its been four releases since its depreciation. I wonder when it really will be removed.

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.

3 participants