Re: [Dri-devel] DRM patch for Linux 2.4.0-prerelease

Re: [Dri-devel] DRM patch for Linux 2.4.0-prerelease

[Keith Whitwell]

Rik,

It looks like this patch goes further than syncing with xfree 4.0.2, but syncs
with the dri trunk instead.  There has been a version bump in the mga drm
module on the dri trunk to add a 'blit' ioctl.  XFree 4.0.2 will barf on this.

As a broader question:  All our version checking (in client drivers and DDX
drivers) check

	found major == expected major
	found minor == expected minor 
	found patch >= expected patch

and if they don't receive this, they refuse to play.

As I understood it, the major number is bumped on backwards-incompatible
changes, the minor number on backwards-compatible changes and the patch on all
other changes, though in practise never.

Thus, wouldn't the appropriate test be:

	found major == expected major
	found minor >= expected minor
	(no test on patch)

This seems to match the semantics of the 3 numbers better?

Keith
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

Re: [Dri-devel] DRM patch for Linux 2.4.0-prerelease

[Rik Faith]

On Thu  4 Jan 2001 14:27:22 -0700,
   Keith Whitwell <keithw@valinux.com> wrote:
> It looks like this patch goes further than syncing with xfree 4.0.2,
> but syncs with the dri trunk instead.  There has been a version bump
> in the mga drm module on the dri trunk to add a 'blit' ioctl.  XFree
> 4.0.2 will barf on this.

You are correct.

For anyone using XFree86 4.0.2 or tracking what we'd like to be included
in Linux 2.4.0, please ignore all the drivers/char/drm/mga* diffs in the
last patch that I sent.  Ignoring those diffs will provide compatibility
with XFree86 4.0.2 for the MGA driver.

Sorry for the confusion.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/