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:17:54PM +0100, Dave Airlie wrote:
> Lets take an example, I'm DA graphics card vendor, I write a DRI driver
> for my brand new 3d graphics cards (they rock btw :-), people buy loads of
> them, I want to give them something on my website that they can deploy to
> use their new card, like a driver for ANotherOS. Now I just want to give
> them an XFree DDX, DRI driver and a drm module (in source form, that they
> can use no matter what kernel), now at the moment no matter what kernel
> they have, the DRM is a completly separate entity - the DRM code deals
> with it,
>
> If we make a library split that sits inside the kernel, their DRM can
> stop working if someone busts the interface, hence the idea of having the
> core reg/dereg in the kernel, and locking it down, then they can ship a
> complete DRM source tree, and do as they wish as long as they interface
> properly with the core...

And with each distro kernel update they have to reinstall the damn thing.
If you absolutely want people to use your driver on older kernels add the
right KERNEL_VERSION (or DRI_VERSION if you want to abstract this out some
way) for older ones.

Again, how is drm different from scsi or net or whatever drivers except
that you need a big userlevel component aswell?
-
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:0.091 / U:6.912 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site