Re: [git pull] drm request 3
From: Maarten Maathuis
Date: Thu Mar 04 2010 - 16:27:26 EST
On Thu, Mar 4, 2010 at 7:18 PM, Linus Torvalds
> Hmm. What the hell am I supposed to do about
> (II) NOUVEAU(0): [drm] nouveau interface version: 0.0.16
> (EE) NOUVEAU(0): [drm] wrong version, expecting 0.0.15
> (EE) NOUVEAU(0): 879:
You can update your userspace components. No compatibility is offered
between versions in any direction.
> What happened to the whole backwards compatibility thing? I wasn't even
> warned that this breaks existing user space. That makes it impossible to
> _test_ new kernels. Upgrading X and the kernel in lock-step is not a valid
> model, lots of people are just using some random distribution (F12 in my
> case), and you just broke it.
> I see the commit that does this was very aware of it:
> commit a1606a9596e54da90ad6209071b357a4c1b0fa82
> Author: Ben Skeggs <bskeggs@xxxxxxxxxx>
> Date: Fri Feb 12 10:27:35 2010 +1000
> drm/nouveau: new gem pushbuf interface, bump to 0.0.16
> This commit breaks the userspace interface, and requires a new libdrm for
> nouveau to operate again.
> The multiple GEM_PUSHBUF ioctls that were present in 0.0.15 for
> compatibility purposes are now gone, and replaced with the new ioctl which
> allows for multiple push buffers to be submitted (necessary for hw index
> buffers in the nv50 3d driver) and relocations to be applied on any buffer.
> A number of other ioctls (CARD_INIT, GEM_PIN, GEM_UNPIN) that were needed
> for userspace modesetting have also been removed.
> Signed-off-by: Ben Skeggs <bskeggs@xxxxxxxxxx>
> Signed-off-by: Francisco Jerez <currojerez@xxxxxxxxxx>
> but why the hell wasn't I made aware of it before-hand? Quite frankly, I
> probably wouldn't have pulled it.
> We can't just go around breaking peoples setups. This driver is, like it
> or not, used by Fedora-12 (and probably other distros). It may say
> "staging", but that doesn't change the fact that it's in production use by
> huge distributions. Flag days aren't acceptable.
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> Dri-devel mailing list
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/