Announcement

Collapse
No announcement yet.

Lightspark May Work Towards A Gallium3D State Tracker

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

  • #46
    Originally posted by NoEffex View Post
    Then I wouldn't use flash LOL
    Fair enough

    Comment


    • #47
      There is a sticky... I just can't edit the damn thing any more

      http://www.phoronix.com/forums/showthread.php?t=7032

      Originally posted by jakubo View Post
      hi, as was mentioned before i thought that gallium was created to make things simple, and to implement features htat might not be native to the hardware.
      and talking of that. i thought that there would be a VDPAU state tracker (even for ati cards) to resolve the discussion about flash-y things.
      Gallium3D is a new low-level API to encapsulate the functionality of a modern shader-based GPU and allow the same functionality to be shared by multiple high-level APIs (state trackers). First step is to get the existing high level APIs running over Gallium3D drivers.

      Originally posted by jakubo View Post
      somehow gallium starts sounding to me like another mesa version. why are there so many other things apart from opengl and directX. are they not up to the task? what is gallium? what is mesa then? why DRI and DRM...??? which one adresses to the hardware directly? sounds like a lot of redundancy to me...
      Mesa implements an OpenGL-like API and has an existing HW driver layer. For each GPU, common mesa code makes up 90-95% of the "Mesa driver" while the HW-specific driver code provides the other 5-10%. Gallium3D drivers replace the HW driver layer (only used for Mesa) with a new driver layer useable by other state trackers, but does not replace the other 90-95% of Mesa.

      3D graphics operations used to go through the X server, then the X server would call Mesa. Running 3D calls through the X server allowed X to manage windows and Mesa to draw into those windows, but with some overhead. The Direct Rendering Infrastructure (DRI) was developed to let applications call Mesa directly and have Mesa check with the X server to see if the target window had moved since the last call. The Direct Rendering Manager (DRM) is the kernel driver which makes up part of the Direct Rendering Infrastructure.

      DRI is a protocol; DRM is a driver component.

      Comment


      • #48
        Originally posted by V!NCENT View Post
        Now give me Coreboot and I'll jump through the roof
        I second that, my friend.

        Comment

        Working...
        X