A Big Comparison Of The AMD Catalyst, Mesa & Gallium3D Drive

[agd5f]

They are in drm-next which Dave will ask Linus to merge soon.

[agd5f]

Here's the basics (not sure this is 100% right, doing this from memory):
#clone Linus tree:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
cd linux-2.6
# check out 2.6.37 on a new branch called my-2.6.37
git checkout -b my-2.6.37 v2.6.37
#add Dave's tree:
git remote add airlied git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git
# fetch the updates from Dave's tree
git fetch airlied
# merge drm-next into the current branch
git pull airlied/drm-next

[yotambien]

I unpacked the 2.6.37 tarball. Not sure what to do next

lol you didn't get too far.

Very interesting question, though. I don't know how to do it myself.

[pingufunkybeat]

You could pull Linus' 2.6.37 final from git, then only merge the drm changes, leaving the other stuff untouched.

It's possible with git, but you might run into a conflict or two, which you'll have to resolve.

[RealNC]

Wouldn't that leave me with an rc8 kernel instead of .37 final?

[agd5f]

I unpacked the 2.6.37 tarball. Not sure what to do next in order to update its DRM drivers :-P

You can't use a tarball to do a git merge. You need to clone either Linus' tree (http://git.kernel.org/?p=linux/kerne....git;a=summary) or Dave's (http://git.kernel.org/?p=linux/kerne...ed/drm-2.6.git) and then add the other one as a remote, fetch the branch you want, do the merge and resolve any conflicts. It's probably easiest to just check out Dave's drm-next branch (2.6.37-rc8 based) and use that directly:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git
cd drm-2.6
git checkout -b drm-next origin/drm-next

[RealNC]

I unpacked the 2.6.37 tarball. Not sure what to do next in order to update its DRM drivers :-P

[agd5f]

I asked this many, many times, but never got an answer: Can I use the development DRM drivers on the current stable kernel? If so, how?

You can either use the drm development tree as is, or merge the changes in drm-next into your current kernel tree (2.6.37) using git.

[RealNC]

The drm pageflipping patches are scheduled to go upstream in 2.6.38, so for now you'll need to use development versions. As for the 2D tiling patches, they require 2.6.37 and probably some more stability testing before I commit them. Hopefully after I pull the ddx pflip stuff into master I'll have some time to get them integrated.

I asked this many, many times, but never got an answer: Can I use the development DRM drivers on the current stable kernel? If so, how?

[pingufunkybeat]

Woah, exciting things ahead! Thanks.