Announcement

Collapse
No announcement yet.

Nouveau X.Org Driver Adds Maxwell & GLAMOR Acceleration Support

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Nouveau X.Org Driver Adds Maxwell & GLAMOR Acceleration Support

    Phoronix: Nouveau X.Org Driver Adds Maxwell & GLAMOR Acceleration Support

    The Nouveau X.Org driver (xf86-video-nouveau) now has basic support for NVIDIA's newest Maxwell graphics processor. Related to that, there's also GLAMOR 2D acceleration support available within the Nouveau DDX...

    http://www.phoronix.com/vr.php?view=MTcyNDM

  • cb88
    replied
    Originally posted by zanny View Post
    Wayland the protocol requires EGL. Any hardware that supports EGL will support OpenGL, or at least OpenGL ES, in some form - whatever form, it will be more than enough to render applications. It is perfectly safe to assume when writing against Wayland that you have working 3d support, albeit you can only really assume GLES because Wayland is already running on phones like the Jolla.
    No... https://tecnocode.co.uk/2013/02/18/w...uffer-backend/ the hardware does not have to support EGL or opengl or anything AFAIK.

    Also see here https://gitorious.org/weston/pwithna...f59dee00177fbd

    Leave a comment:


  • cb88
    replied
    Originally posted by zanny View Post
    Wayland the protocol requires EGL. Any hardware that supports EGL will support OpenGL, or at least OpenGL ES, in some form - whatever form, it will be more than enough to render applications. It is perfectly safe to assume when writing against Wayland that you have working 3d support, albeit you can only really assume GLES because Wayland is already running on phones like the Jolla.
    No... https://tecnocode.co.uk/2013/02/18/w...uffer-backend/ the hardware does not have to support EGL or opengl or anything AFAIK.

    Leave a comment:


  • zanny
    replied
    Originally posted by JS987 View Post
    There is difference between Wayland compositor and Wayland application.
    Wayland the protocol requires EGL. Any hardware that supports EGL will support OpenGL, or at least OpenGL ES, in some form - whatever form, it will be more than enough to render applications. It is perfectly safe to assume when writing against Wayland that you have working 3d support, albeit you can only really assume GLES because Wayland is already running on phones like the Jolla.

    Leave a comment:


  • JS987
    replied
    Originally posted by cb88 View Post
    Most any of the Wayland Compositors will be using OpenGL or something similar for acceleration so stop being pedantic.
    There is difference between Wayland compositor and Wayland application.

    Leave a comment:


  • cb88
    replied
    Originally posted by JS987 View Post
    Wayland can't use openGL because Wayland does no rendering. If application uses openGL depends on application or its dependencies e.g. Qt / Gtk+ / Cairo etc.
    Most any of the Wayland Compositors will be using OpenGL or something similar for acceleration so stop being pedantic.

    Leave a comment:


  • JS987
    replied
    Originally posted by AJenbo View Post
    Wayland uses openGL natively. GLAMOR basically allows Xorg to do the same.
    Wayland can't use openGL because Wayland does no rendering. If application uses openGL depends on application or its dependencies e.g. Qt / Gtk+ / Cairo etc.

    Leave a comment:


  • smitty3268
    replied
    Originally posted by mark45 View Post
    Wayland (not XWayland or Xorg) doesn't need Glamor, right? It's purely an X.org issue, correct?
    Yeah, Glamor is a hardware accelerated implementation of the XRender API - which as the name suggests, is only used in X applications.

    Leave a comment:


  • Ericg
    replied
    Originally posted by deppman View Post
    The other day I upgraded to the nv blob to latest beta drivers. Then I went merrily on my way to continue my days work. All my desktop apps worked fine, and desktop compositing looked as smooth as normal on my gtx 660.

    I noticed about an hour later that kde-jockey was prompting me to select a driver - and that I had been using Nouveau during that time and hadn't even noticed. It had just worked. That's high praise, IMO.

    With dynamic reclocking and recent NV contributions, Nouveau is starting to look pretty nice. I'll definitely keep an eye on it!
    Oh yeah, nouveau is beautiful if you're just doing desktop stuff and general-usage stuff. Where it falls short is games and (possibly) video rendering because of it lack of reclocking.

    Leave a comment:


  • deppman
    replied
    Nouveau driver might sneak up on us

    The other day I upgraded to the nv blob to latest beta drivers. Then I went merrily on my way to continue my days work. All my desktop apps worked fine, and desktop compositing looked as smooth as normal on my gtx 660.

    I noticed about an hour later that kde-jockey was prompting me to select a driver - and that I had been using Nouveau during that time and hadn't even noticed. It had just worked. That's high praise, IMO.

    With dynamic reclocking and recent NV contributions, Nouveau is starting to look pretty nice. I'll definitely keep an eye on it!

    Leave a comment:

Working...
X