Bug 10576

Links to drm and kernels git's  that have introduced incompatibility:

http://gitweb.freedesktop.org/?p=mesa/drm.git;a=commitdiff;h=f2db76e2f206d2017f710eaddc4b33add4498898

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=e0dc0d8f4a327d033bfb63d43f113d5f31d11b3c

Someone has to change the name but who?

(In reply to comment #1)
> Links to drm and kernels git's  that have introduced incompatibility:
> 
> http://gitweb.freedesktop.org/?p=mesa/drm.git;a=commitdiff;h=f2db76e2f206d2017f710eaddc4b33add4498898
> 
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=e0dc0d8f4a327d033bfb63d43f113d5f31d11b3c
> 
> Someone has to change the name but who?
> 

vm_insert_pfn first appears in the kernel in the 2.6.21-rc series.
In drm_compat.c it is not included if the kernel version >= 2.6.21, when the
symbol DRM_FULL_MM_COMPAT is defined. 

The semantics of the two functions, although they are looking very different are the same. The one in the mainstream kernel should be used if there is a clash.

I'm not sure why it appears in Ubuntu 2.6.20. I think you need to ask the Ubuntu guys. 

/Thomas

 

(In reply to comment #2)
> I'm not sure why it appears in Ubuntu 2.6.20. I think you need to ask the
> Ubuntu guys. 

It's hardly uncommon for a distro to choose a kernel (2.6.20), and then pull selectively from patches intended for a newer release without updating their kernel version to describe itself as that newer release (which it isn't).

What would you have the Ubuntu maintainers do instead?

(In reply to comment #3)
> (In reply to comment #2)
> > I'm not sure why it appears in Ubuntu 2.6.20. I think you need to ask the
> > Ubuntu guys. 
> It's hardly uncommon for a distro to choose a kernel (2.6.20), and then pull
> selectively from patches intended for a newer release without updating their
> kernel version to describe itself as that newer release (which it isn't).
> What would you have the Ubuntu maintainers do instead?

Actually I think that's fine. I cant really figure out why they would want to pull vm_insert_pfn, since AFAICT it is only used by DRM and cell, but anyway they are free to do what they want.

The more important question raised here is what are the DRM developers expected to do about this? Should we maintain compatibility with all more or less selectively patched kernels from all distros?

Thomas

We used to do this, but it takes a fair bit of effort... and I really couldn't be bothered, I run ubuntu here and I just ifdef around it rather than try to figure out what they did to their kernel..