Re: is there a fork between drm from DRI and drm from kernel.org?

[Dave A. <ai...@li...>]

> Sorry for the question, but browsing the mailing list did not give any
> answer, other then that you need to build drm WITH current Linux kernel,
> but why is it not in THE current Linux kernel?

There is a delay between patches going into the CVS tree and the kernel,
usually because of the kernel merge cycles, most of the latest CVS should
be in my git tree .. and that is what I'll merge to Linus when he next
opens up for merges, I can't submit major patches to the kernel outside of
the merge cycles...

> with that kind of chipset and I can do the merge, but I don't know what
> to merge into what.

The mach64 DRM is insecure, it needs securing before it can be included in
the kernel...

> I saw that those trees are forked, my interest was in mga and mach64
> chip families. MGA in the kernel is dated
>
> DRIVER_DATE  "20050607"
>
> whereas DRI version is
>
> DRIVER_DATE  "20051102"
>
> But, kernel version is not a superset of DRI version. Function name
> changes, and even interface changes (i.e. parameters for functions).

The  kernel also has no support for DRM drivers acting as full PCI
drivers, the CVS tree still has this, at some point I'll start fixing up
the kernel to support fb and drm devices on the same PCI device...

> I wanted to get myself linux kernel updated to latest DRI code, but I
> don't know what to do to be generally productive, i.e. so those patchese
> may be merged into kernel tree.
>
> I figured that Dave Airlie is managing the kernel.org version of
> drivers/char/drm, but who is in charge of drm/shared-core
> /drm/linux-core?
>

Usually myself and Eric Anholt are the main hackers, but everyone in the
DRI/X.org team have DRM commit access.. myself and Eric push them to
Linux/FreeBSD projects..

Dave.

-- 
David Airlie, Software Engineer
http://www.skynet.ie/~airlied / airlied at skynet.ie
Linux kernel - DRI, VAX / pam_smb / ILUG