Announcement

Collapse
No announcement yet.

RadeonHD Driver To Use AtomBIOS

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

  • #46
    Originally posted by Louise View Post
    I was wondering, when it have been decided to stay with TTM or move to Intel's GEM. Does that change anything in regards to the ati and radeonhd drivers?
    The memory management code is all in the kernel (the drm component) so most of the work is outside the ati and radeonhd drivers. Once memory management is up and running, however, both drivers will need to be modified to use the drm's memory manager rather than performing those functions itself.

    Kernel modesetting is easier by comparison, since the driver can choose whether or not it wants to use KMS, but AFAIK memory management will require more coordination across the components.

    As far as TTM vs GEM goes, the general consensus seems to be to use the GEM calls for "core" functions, since non-driver components such as DRI2 need to use the memory manager and therefore require commonality across drivers, and to allow the rest of the API calls to be driver-specific. There seem to be some areas where TTM is preferable, at least for discrete graphics, and it sounds like the final solution is likely to be a mix of GEM and TTM concepts.

    The TTM/GEM discussion may have delayed development of memory manager and kernel modesetting by a month or two but it was probably all for the best, since the devs generally seem to feel that some of the ideas in GEM help to address some long-standing problems.
    Last edited by bridgman; 07-06-2008, 01:41 PM.

    Comment


    • #47
      Originally posted by bridgman View Post
      The memory management code is all in the kernel (the drm component) so most of the work is outside the ati and radeonhd drivers. Once memory management is up and running, however, both drivers will need to be modified to use the drm's memory manager rather than performing those functions itself.

      Kernel modesetting is easier by comparison, since the driver can choose whether or not it wants to use KMS, but AFAIK memory management will require more coordination across the components.
      Hmm not really, the plan to stop the X server running as root, means you have to use kernel based modesetting with a DRM exposed acceleration architecture. This is part of securing X properly not with duct tape and bonghits.

      There will be one kernel memory manager for radeon and one modesetting implementation, Userspace drivers are for accel only via submission of command buffers to the DRM.

      Dave.

      Comment

      Working...
      X