From: Ben Widawsky <benjamin.widawsky@intel.com>
To: Intel GFX <intel-gfx@lists.freedesktop.org>
Cc: Kristen Carlson Accardi <kristen@linux.intel.com>
Subject: [ANNOUNCE] Broadwell temporary branch
Date: Mon, 24 Feb 2014 18:25:08 -0800 [thread overview]
Message-ID: <20140225022508.GA28034@intel.com> (raw)
In response to the demand for Broadwell features and fixes which are not
yet merged in our upstream drm-intel repository
(http://cgit.freedesktop.org/drm-intel/) I will be maintaining a branch
in my freedesktop repository with some of the features and fixes that I
have been using myself.
Platform branches have not worked particularly well for us in the past,
and I am hopeful that the repository will be [extremely] short lived
because many of the patches I am keeping are either obvious fixes, or
decently reviewed patch series. At the very least it will be maintained
until Daniel returns from vacation next week (but I do expect it to last
at least a few weeks past that).
The branch will be a rebasing branch from the upstream
drm-intel-nightly, and should not be expected to be as stable as
upstream Broadwell support. Please only use this if you need to use a
specific feature, or fix in the branch.
The current series has the following:
Broadwell hardware semaphore support - review comments pending.
Broadwell 4GB GGTT + PPGTT cleanups - reviewed
Broadwell RC6 support - review comments pending
FBC Support
Random fixes from Mika - I have the older series here.
Likely coming soon:
Runtime PM support for Broadwell from Paulo
http://cgit.freedesktop.org/~bwidawsk/drm-intel/log/?h=broadwell
Thanks for your attention.
--
Ben Widawsky, Intel Open Source Technology Center
reply other threads:[~2014-02-25 2:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20140225022508.GA28034@intel.com \
--to=benjamin.widawsky@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=kristen@linux.intel.com \
/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