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

Is it possible to use it with DRM backend in weston? #22

Open
ssdasilva opened this issue Jun 19, 2023 · 4 comments
Open

Is it possible to use it with DRM backend in weston? #22

ssdasilva opened this issue Jun 19, 2023 · 4 comments

Comments

@ssdasilva
Copy link

ssdasilva commented Jun 19, 2023

I am using the framebuffer-vncserver application with weston compositor using the DRM backend. This application needs to access the framebuffer being used, but when I check the device /dev/fb0 I see that nothing is being written there (which indicates that the /dev/fb0 device is not being used). I have searched for ways of accessing the framebuffer used in the DRI, but I had no success. Thus, is it possible to directly access the framebuffer in the Weston DRM backend? I know there is the fbdev-backend in weston. However, I have trouble using it with openGL. Furthermore the fbdev-backend will be deprecated in newer versions of weston (Thus, using the DRM backend is the preferred way). Could anyone help me? Is it possible to add instructions to do it in the README, or add some documentation for the DRM backend?

@dedounet
Copy link

+1 !

@ponty
Copy link
Owner

ponty commented Sep 24, 2023

If you have no working /dev/fb0 then you can't use this program.

@dedounet
Copy link

dedounet commented Oct 2, 2023

And what about abinding to /dev/dri/card0 ?

@ponty
Copy link
Owner

ponty commented Oct 2, 2023

You can use any file if it is a Linux framebuffer, but I don't think that /dev/dri/card0 is a Linux framebuffer.

Check the command-line help

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