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

Develop in the open #149

Closed
wwahammy opened this issue Jan 25, 2019 · 1 comment
Closed

Develop in the open #149

wwahammy opened this issue Jan 25, 2019 · 1 comment

Comments

@wwahammy
Copy link

In at least a few forum posts, such as (https://support.displaylink.com/forums/287786-displaylink-feature-suggestions/suggestions/16639654-linux-wayland-support), it was suggested that the community develop functionality that doesn't exist. Unfortunately, that would be pointless as pull requests are not considered for actual merging as described in comments for #148, #146, #142. Additionally, the core driver code is provided as binary. I can't for the life of me figure out why you won't open source some code that you clearly don't not care about maintaining all that much.

@displaylink-dkurek
Copy link
Contributor

Development for Wayland is in progress (as Wim wrote in the link you have
provided) mainly in other components, like GNOME or Mutter. We had also added
support for different pixel formats (e4ea8d3) to EVDI as a possible optimization
of pixel path. Any PR is welcome and is considered for merge but sometimes we
already have those changes and are testing them before a push.

We have explained why we are providing part of the solution in binary format,
please take a look at our support page.

Hope I have helped explaining things a bit.
Closing.

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

No branches or pull requests

2 participants