[Intel-gfx] Requesting proposals for a 2.7.1 maintenance release

[Eric Anholt]

On Wed, 2009-05-06 at 12:54 -0400, Kristian Høgsberg wrote:
> On Mon, May 4, 2009 at 8:24 PM, Eric Anholt <eric at anholt.net> wrote:
> > On Mon, 2009-05-04 at 13:29 -0700, Carl Worth wrote:
> >> I've been told that some recent commits to the master branch are major
> >> bug fixes that warrant a 2.7.1 release soon. I'll be glad to make that,
> >> but first I need anyone that wants to see a fix in 2.7.1 to propose
> >> fixes for me to cherry pick.
> >
> > Definitely these two.  Reviewed the first.
> >
> > commit 1142353b487c155a31011923fbd08ec67e60f505
> > Author: Keith Packard <keithp at keithp.com>
> > Date:   Fri May 1 11:44:13 2009 -0700
> >
> >    intel_batch_start_atomic: fix size passed to intel_batch_require_space (*4)
> >
> > commit 11a853bd8e5d907fe7f5bd907453bcdac9032861
> > Author: Keith Packard <keithp at keithp.com>
> > Date:   Fri May 1 11:51:13 2009 -0700
> >
> >    Hold reference to video binding table until all rects are painted.
> >
> > But probably also this one:
> >
> > commit 8255cca2c9092f7ecb798944aa8f03fa3efcfa6c
> > Author: Keith Packard <keithp at keithp.com>
> > Date:   Fri May 1 18:34:43 2009 -0700
> >
> >    Split i915 textured video commands to fit into batch buffers.
> 
> Agree with those, and I'd suggest also:
> 
> commit d7ca870e1ce251d42e3689a8e1e7d080ab1325fb
> Author: Albert Damen <albrt at gmx.net>
> Date:   Sun Apr 5 16:36:35 2009 +0200
> 
>     Fix crash with XV with large virtual display
> 
>     If a virtual display with width > 2048 is used, the first time
>     an XV buffer is needed will result in a BadAlloc error message,
>     but the next time X would crash.
> 
> and this one, not sure why Eric didn't recommend that, but I guess it
> isn't as critical a fix, since it just the shutdown path:
> 
> commit e5e0fb846bda3e1757b89e50d5244d28457b9fe3
> Author: Keith Packard <keithp at keithp.com>
> Date:   Fri May 1 12:26:04 2009 -0700
> 
>     Call down to lower CloseScreen before shutting down DRM allocator
> 
>     Lower level functions will destroy objects that are managed by the DRM
>     allocator, so make sure those are done before the allocator shuts down.

The init/close paths are a trainwreck, and I was waiting for it to
settle a while.  Also, would need testing across the pile of
combinations.

We should probably also get the UXA non-DRI fallback fixes into a
release sooner rather than later.
https://bugs.freedesktop.org/show_bug.cgi?id=21575 includes identities
of at least part of what's required.

-- 
Eric Anholt
eric at anholt.net                         eric.anholt at intel.com


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/intel-gfx/attachments/20090506/49814ec0/attachment.sig>