From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Subject: [ANNOUNCE] xf86-video-intel 2.14.902
Date: Tue, 29 Mar 2011 11:53:59 +0100 [thread overview]
Message-ID: <b9dded$ifkl6u@orsmga002.jf.intel.com> (raw)
A bit later than everyone expected as it took a fair while to get our
overall regression count down, it's time for a new release candidate.
Still nothing exciting happening here, as you would expect once we were in
the release phase, with just a couple of bug fixes.
Please test!
-Chris
Chris Wilson (7):
Update priv->stride after bo reallocation
Give each user of tiling separate xorg.conf options
dri: Disable page-flip between a tiled buffer and a linear scanout
i915/video: Clip indirect Xv output
Use the per-generation batch context switch for atomic sequences
NEWS: Entry for 2.14.902 snapshot
configure: version bump for 2.14.902 snapshot
Keith Packard (4):
dri2: Make DRI2FrameEvent public and use instead of void *
Handle drawable/client destruction in pending swaps/flips
Skip client and drawable resource delete calls when deleting frame event
Recover from i830_dri2_add_frame_event out-of-memory condition
git tag: 2.14.902
http://xorg.freedesktop.org/archive/individual/driver/xf86-video-intel-2.14.902.tar.bz2
MD5: 7c48151a87311beea39837812e7b9e2b xf86-video-intel-2.14.902.tar.bz2
SHA1: 552d6d1be754c974d140763232a2c17361d9a625 xf86-video-intel-2.14.902.tar.bz2
http://xorg.freedesktop.org/archive/individual/driver/xf86-video-intel-2.14.902.tar.gz
MD5: 7147e69457eb18d92a1430f77fefae89 xf86-video-intel-2.14.902.tar.gz
SHA1: 3e2b06b84901dc5bd8dc0e93ca28e9e6c2591c44 xf86-video-intel-2.14.902.tar.gz
--
Chris Wilson, Intel Open Source Technology Centre
next reply other threads:[~2011-03-29 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 10:53 Chris Wilson [this message]
2011-03-29 11:11 ` [ANNOUNCE] xf86-video-intel 2.14.902 Christophe Gallaire
2011-03-29 16:55 ` Julien Cristau
2011-03-30 1:48 ` Cyril Brulebois
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='b9dded$ifkl6u@orsmga002.jf.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox