So upstream is likely not going to take this patch in time for karmic, they would rather focus upon getting the X server to be able to fallback later in the detection process.
I would like to propose carrying this patch (or at least a variation of this patch) for karmic, with the intention of dropping it during karmic+1 or karmic+2, basically whenever upstream would have the xserver more gracefully allowing falling back onto another driver.
I don't expect regressions in doing this, but if there was going to be any regression, the worst would be user's with the device ID's 00f0->00ff and 02e0->02e4 not being able to boot into the 'nv' driver, and falling back to VESA.
So upstream is likely not going to take this patch in time for karmic, they would rather focus upon getting the X server to be able to fallback later in the detection process.
http:// lists.x. org/archives/ xorg-devel/ 2009-September/ 002019. html
I would like to propose carrying this patch (or at least a variation of this patch) for karmic, with the intention of dropping it during karmic+1 or karmic+2, basically whenever upstream would have the xserver more gracefully allowing falling back onto another driver.
I don't expect regressions in doing this, but if there was going to be any regression, the worst would be user's with the device ID's 00f0->00ff and 02e0->02e4 not being able to boot into the 'nv' driver, and falling back to VESA.