From: Chris Wilson <chris@chris-wilson.co.uk>
To: intel-gfx@lists.freedesktop.org
Subject: [ANNOUNCE] xf86-video-intel 2.14.901
Date: Wed, 02 Mar 2011 17:56:25 +0000 [thread overview]
Message-ID: <1bdc18$jochvd@fmsmga002.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2784 bytes --]
Some time ago, Cyril asked me if there might be a snapshot for 2.15.
The good news is that today is that day! And here it is...
Just a load of bug fixes, no major performance improvements or other
changes. As usual, please test and let us know of any regressions.
-Chris
Adam Jackson (1):
Fix IGD and IGDNG constants to be comprehensible
Bryce Harrington (2):
Check return value of uxa_acquire_solid() since it can return NULL
Quell excessively verbose vblank counter failed error messages
Chris Wilson (19):
Remove unused struct _intel_memory definition
Remove unused GTT/Map sizes and addresses
Delete some dead code
Remove bitrotted, but fortunately unused, I830CrtcPrivate
Remove unused I830Output
Cache the fixed crtc<->pipe relationship
Delete unused memory allocation flags.
Create the UXA generational resources during screen create
uxa: Only recreate the glyph cache on *generational* updates
i915: Remove unused 'num_floats' variable
i915: Remove unused 'w' and 'h'
Enable conditional compilation of asserts
Rename 'intel' backlight to match upstream name in 2.6.38
uxa: Undo damage translation before appending
i965: Remove broken maximum base addresses from video
uxa: Fallback if the temporary is too large
dri: Protect against destroying a foreign DRI drawable
NEWS: Add entry for 2.14.901 snapshot
configure: Bump for 2.14.901 snapshot
Cyril Brulebois (5):
xvmc: Get rid of unused variables.
xvmc: Silence gcc, add parentheses around assignment.
xvmc: Silence gcc, add parentheses around arithmetic.
xvmc: Silence gcc, adding a cast to work around signedness issues.
xvmc: Stop using uninitialized variable.
Daniel Vetter (1):
Fix relaxed tiling on gen2
Eric Anholt (1):
Quiet compiler warning about is_affine_src same way we do is_affine_mask.
Javier Jardón (1):
Update autotools configuration
Simon Farnsworth (1):
Fix textured video when destination is larger than screen
Xiang, Haihao (2):
Correct offset of planes within clipped window
Fix an error in 4c4ad555564a80311df1a4b762eb1e119c6d95fb.
git tag: 2.14.901
http://xorg.freedesktop.org/archive/individual/driver/xf86-video-intel-2.14.901.tar.bz2
MD5: 67c4340f491289fa9d56d0a89565f130 xf86-video-intel-2.14.901.tar.bz2
SHA1: 8d6a6dadc5dd3f1261f23e2f05f9f04bf01a47b5 xf86-video-intel-2.14.901.tar.bz2
http://xorg.freedesktop.org/archive/individual/driver/xf86-video-intel-2.14.901.tar.gz
MD5: 0c68bd7b2420c2a19eaf0cb770f6a6a4 xf86-video-intel-2.14.901.tar.gz
SHA1: 9534a581c02cb11817dcebc81ce7db21f1f1a4d2 xf86-video-intel-2.14.901.tar.gz
--
Chris Wilson, Intel Open Source Technology Centre
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2011-03-02 17:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 17:56 Chris Wilson [this message]
2011-03-03 1:09 ` [ANNOUNCE] xf86-video-intel 2.14.901 Cyril Brulebois
2011-03-03 11:06 ` Chris Wilson
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='1bdc18$jochvd@fmsmga002.fm.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