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

kdbus not mainlined yet #41

Closed
steverweber opened this issue Aug 10, 2015 · 6 comments
Closed

kdbus not mainlined yet #41

steverweber opened this issue Aug 10, 2015 · 6 comments

Comments

@steverweber
Copy link

could dbus be used instead of kdbus?

thanks/

@steverweber steverweber changed the title kdbus not landing in mainline kdbus not mainlined yet Aug 10, 2015
@steverweber
Copy link
Author

never mind...

@vindicatorr
Copy link

@steverweber I think your question is still valid. I don't think kdbus will build for kernel 4.6+.
I personally attempted to build for 4.7RC# and it fails because code had moved in 4.6.
gregkh/kdbus#38

@albfan
Copy link
Owner

albfan commented Jun 23, 2016

correct me if I'm wrong, I'm not an expert here.

https://www.reddit.com/r/linux/comments/3auufg/eli12_dbus_vs_kdbus_vs_sdbus/

kdbus is dbus on kernel, so there's no "instead of", simply kdbus is not avaliable by default. There's no way to listen to wifi interface messages without enabling kdbus on systemd.

It's relative easy to enable kdbus on systemd, don't know the reasons to release it without it by default.

@albfan
Copy link
Owner

albfan commented Jun 26, 2016

Since version 220 systemd has kdbus enabled by default:

systemd/systemd@1b09f54#diff-67e997bcfdac55191033d57a16d1408aR1206

albfan added a commit that referenced this issue Jun 26, 2016
albfan added a commit that referenced this issue Jun 26, 2016
@vindicatorr
Copy link

I was going to give a heads-up regarding systemd having kdbus enabled vs having it in the kernel, but now I'm now wondering if I should even bother if comments are just going to be deleted.

@albfan
Copy link
Owner

albfan commented Jun 26, 2016

That's not the question of issue, which indeed has been resolved.

You can open another issue if that improves in some way miraclecast.

Try to focus on precise issues and detailed solutions that's the purpose of an issue tracker

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

3 participants