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

directfb: Initial support #454

Closed
wants to merge 1 commit into from
Closed

directfb: Initial support #454

wants to merge 1 commit into from

Conversation

theuni
Copy link
Contributor

@theuni theuni commented Sep 30, 2011

Directfb has recently gained support for Mesa/DRM for GLES2.0 acceleration.
This means we can now run without X on supported platforms. This has been
tested on a SandyBridge Macbook Pro.

Limitations:

  • Depends on latest DirectFB/Mesa. Oneric should have all that's needed.

Issues:

  • Current DirectFB/Mesa has a bug causing the screen to be shown upside-down.
  • Current DirectFB/Mesa fails to compile our shaders.
  • Current DirectFB does not yet have have vsync hooked up.

Upstream is aware of these issues and is very eager to fix them for us in the
next few days so that they can feature XBMC support with their next release.

TODO:

  • Hook up resolution switching in XBMC (currently it's done via a config file)
  • Decide whether we need to hook up windowing functions (I say no.)
  • Implement ImageProviders for hardware-accelerated image decodes.
  • Cleanup the configure logic

Directfb has recently gained support for Mesa/DRM for GLES2.0 acceleration.
This means we can now run without X on supported platforms. This has been
tested on a SandyBridge Macbook Pro.

Limitations:
- Depends on latest DirectFB/Mesa. Oneric should have all that's needed.

Issues:
- Current DirectFB/Mesa has a bug causing the screen to be shown upside-down.
- Current DirectFB/Mesa fails to compile our shaders.
- Current DirectFB does not yet have have mesa hooked up.

Upstream is aware of these issues and is very eager to fix them for us in the
next few days so that they can feature XBMC support with their next release.

TODO:
- Hook up resolution switching in XBMC (currently it's done via a config file)
- Decide whether we need to hook up windowing functions (I say no.)
- Implement ImageProviders for hardware-accelerated image decodes.
- Cleanup the configure logic
@theuni
Copy link
Contributor Author

theuni commented Sep 30, 2011

I tried to come up with a way to split this up for easier review, but it really only makes sense in one chunk.

The changes are quite un-invasive to the rest of the codebase.

@theuni
Copy link
Contributor Author

theuni commented Mar 20, 2012

Letting this die. While it is interesting as a concept, this would bring in no additional hardware support at the moment.

Much more interesting would be skipping the dfb layer and using mesa+kms directly. See here: http://virtuousgeek.org/blog/index.php/jbarnes/2011/10/31/writing_stanalone_programs_with_egl_and_

@theuni theuni closed this Mar 20, 2012
@jdembski
Copy link
Contributor

Can someone tell me what "jdembski referenced this pull request from a commit" means? I didn't do that?!

tru pushed a commit to plexinc/plex-home-theater-public that referenced this pull request Jan 31, 2013
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.

None yet

2 participants