lkml.org 
[lkml]   [2004]   [Sep]   [4]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: New proposed DRM interface design
    On Sat, Sep 04, 2004 at 01:12:16AM +0100, Dave Airlie wrote:
    > DRM core - just the stub registration procedure and handling any
    > shared resources like the device major number, and perhaps parts of sysfs
    > and class code. This interface gets set in stone as quickly as possible
    > and is as minimal as can be, (Jon Smirls dyn-minor patch will help a fair
    > bit also). All the core does is allow DRMs to register and de-register in
    > a nice easy fashion and not interfere with each other. This drmcore.o can
    > either be linked into the kernel (ala the fb core) or a module, but in
    > theory it should only really be shipped with the kernel - (for compat
    > reasons the DRM tree will ship it for older systems).

    Ok.

    > DRM library - this contains all the non-card specific code, AGP
    > interface, buffers interface, memory allocation, context handling etc.
    > This is mostly stuff that is in templated header files now moved into C
    > files along the lines of what I've done in the drmlib-0-0-1-branch. This
    > file gets linked into each drm module, if you build two drivers into the
    > kernel it gets shared automatically as far as I can see, if you build as
    > modules they both end up with the code, for the DRM the single card is the
    > primary case so I don't mind losing some resources for having different
    > cards in a machine.

    Ok except you should build this only once.

    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 14:05    [W:9.342 / U:0.036 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site