From: Thierry Reding <thierry.reding@gmail.com>
To: Dave Airlie <airlied@gmail.com>
Cc: dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: -next plans/status
Date: Thu, 6 Nov 2014 17:02:45 +0100 [thread overview]
Message-ID: <20141106160243.GA14873@ulmo.nvidia.com> (raw)
In-Reply-To: <CAPM=9tywXzvOFnpuhQBLy52KF0KEV6EYGB++B6sFKiFDzr9knA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1426 bytes --]
On Mon, Nov 03, 2014 at 08:29:24AM +1000, Dave Airlie wrote:
> So since -rc5/6 cutoff last merge windows was so successful from my
> POV, I think I'll keep trucking with the idea.
>
> Things I have on my radar for this window, outside normal driver pull requests:
>
> a) rockchip drm - this needs IOMMU driver merged first so I can even
> compile it, on hold but shouldn't be a problem if the iommu driver
> gets merged somewhere first.
>
> b) atmel hlcdc - where are we on the precursor patches for this?
>
> c) atomic - Daniel seems to have done a good job pulling the helpers
> in line, Rob, Sean, Collabora - please jump on board and get this
> thing over the line.
>
> d) Exynos/bridge/make my chromebook work upstream patches, where are
> we on these, Ajay/Thierry I believe you are in the know.
Daniel briefly looked at this and was somewhat disgusted with how little
safety this framework has built in. The infrastructure was copied from
DRM panel which therefore suffers from the same shortcomings. I've been
working on a small set of patches to implement some generic mechanism to
add reference counting and such for this type of infrastructure.
Until those patches are ready I think we either can't merge the patches
or we take the risk that drivers will actually use the current fragile
infrastructure in a safe way and then supply the safer infrastructure
later on.
Thierry
[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2014-11-06 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-02 22:29 -next plans/status Dave Airlie
2014-11-03 7:56 ` Oded Gabbay
2014-11-03 10:56 ` Boris Brezillon
2014-11-04 22:10 ` Alex Deucher
2014-11-06 16:02 ` Thierry Reding [this message]
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=20141106160243.GA14873@ulmo.nvidia.com \
--to=thierry.reding@gmail.com \
--cc=airlied@gmail.com \
--cc=dri-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.