[pkg-nvidia-devel] Bug#483650: linux-image-2.6.25-2-686: 'Xen kernel' breaks 'nvidia-kernel-legacy-71xx-source'.

[Lennart Sorensen]

On Sat, Jun 28, 2008 at 02:17:44AM -0400, A. Costa wrote:
> On Fri, 30 May 2008 09:50:12 -0400, Len Sorensen wrote:
> 
> > I am making a patch to fix the legacy driver.  Not a kernel problem.
> 
> About that patch, over on the 96xx branch, your patch is being used:
> 
> 	nvidia-kernel-legacy-96xx-source: Fails to compile with kernel 2.6.25
> 	http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477643
> 
> ...so I was curious if a 71xx version was pending.
> 
> To anybody, I notice upstream has a patch:
> 
> 	Using NVIDIA Linux graphics drivers with Linux 2.6.25
> 	http://www.nvnews.net/vbulletin/showthread.php?t=110088
> 
> ...but it's not clear from the instructions there what the proper
> 'Debian way' to apply it is.   On the 96xx bug (#477643) L. Sorensen
> put two patches, one for 'xen' and another for 96xx:

Well I was waiting to see if it worked and we got it released for 96xx
before doing one for 71xx.

> 	http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=477643#12
> 
> ...where the 96xx patch is identical to upstream's 96xx patch, and the 
> 'xen' is a general tweak for a Debian nv setup script 'usr/src/nv/conftest.sh'.
> 
> Therefore, upstream's 71xx and Sorensen's 'xen' patch together should
> probably work.  But I'm not sure of what the "Debian way" to apply
> those is... preferably it should be in the form of a foolproof
> one-liner that any user can cut n' paste, but no complex 10-step
> recipes that requires checking version numbers, deciding where to put
> files, yadda yadda yadda.
> 
> Pseudo-code might look something like:
> 
> 	PATCHDIR=/tmp/foo; cd $PATCHDIR && wget <upstream URLs> && m-a <pre-patch actions> && patch <whatever> && m-a <post-patch actions>

Well simplest would be if we just get the patch into the package and
release it.  After all that is the supported way to deal with patches in
Debian.

-- 
len Sorensen