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

Framebuffer device for cairo-fb is hardcoded to /dev/fb0. #68

Closed
jimsynz opened this issue May 6, 2024 · 2 comments
Closed

Framebuffer device for cairo-fb is hardcoded to /dev/fb0. #68

jimsynz opened this issue May 6, 2024 · 2 comments

Comments

@jimsynz
Copy link
Contributor

jimsynz commented May 6, 2024

Hi there.

I have a small SPI connected display that I have working using the Linux fbtft driver. I've been struggling to get Scenic to work, and finally managed to get it working by using the cairo-fb driver from main. Unfortunately the driver has the framebuffer device hardcoded to /dev/fb0 and my display is registered as /dev/fb1. I worked around it by symlinking /dev/fb0 to /dev/fb1 and have been rewarded with my scene displaying. Pretty exciting.

Is there any way we can make this a configurable option?

Thanks!

@crertel
Copy link
Contributor

crertel commented May 7, 2024

Ah, I imagine we can figure out something. Thanks for the request!

@crertel
Copy link
Contributor

crertel commented May 7, 2024

Looks like we pass in args here and then add them to the global options here.

That options struct is defined here and then we set the framebuffer name here.

I bet we could just pass this in as another command-line argument, set it on that global struct, load from the global opts struct instead of a c-file constant, and then bob's your uncle.

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