<div dir="ltr">What sort of testing on this series would be most helpful? I figure that you and pq have most of the code review covered, so the main contribution I can make with the hardware available to me is to exercise this on consumer-grade systems like Macbooks with Intel display controllers. Are there are specific use-cases that will put the most stress on your new stuff? I assume that doing some sub-fullscreen OpenGL windows will kick in the overlay selections to test that out.</div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Nov 2, 2017 at 2:05 AM, Ucan, Emre (ADITG/ESB) <span dir="ltr"><<a href="mailto:eucan@de.adit-jv.com" target="_blank">eucan@de.adit-jv.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Daniel,<br>
<br>
Your proposal is exactly what I thought, how it should be.<br>
I am looking forward for next revision of patches.<br>
<span class="im HOEnZb"><br>
Best regards<br>
<br>
Emre Ucan<br>
Engineering Software Base (ADITG/ESB)<br>
<br>
Tel. <a href="tel:%2B49%205121%2049%206937" value="+495121496937">+49 5121 49 6937</a><br>
<br>
> -----Original Message-----<br>
> From: Daniel Stone [mailto:<a href="mailto:daniel@fooishbar.org">daniel@fooishbar.org</a>]<br>
</span><span class="im HOEnZb">> Sent: Mittwoch, 1. November 2017 15:14<br>
> To: Ucan, Emre (ADITG/ESB)<br>
> Cc: <a href="mailto:wayland-devel@lists.freedesktop.org">wayland-devel@lists.<wbr>freedesktop.org</a><br>
> Subject: Re: [PATCH weston v12 00/40] Atomic modesetting<br>
><br>
</span><div class="HOEnZb"><div class="h5">> Hi Emre.<br>
><br>
> On 1 November 2017 at 11:56, Ucan, Emre (ADITG/ESB)<br>
> <<a href="mailto:eucan@de.adit-jv.com">eucan@de.adit-jv.com</a>> wrote:<br>
> > Is this the latest WIP branch to test "<br>
> <a href="https://gitlab.collabora.com/daniels/weston/commits/wip/2017-10/atomic-" rel="noreferrer" target="_blank">https://gitlab.collabora.com/<wbr>daniels/weston/commits/wip/<wbr>2017-10/atomic-</a><br>
> v13" ?<br>
><br>
> Right you are.<br>
><br>
> > In my opinion, it would easier to review/test your patches if you can<br>
> separate them in multiple patch series.<br>
> ><br>
> > For example, you can send at first up to "compositor-drm: Atomic<br>
> modesetting support". Commit message states that it enables atomic API<br>
> support for weston.<br>
> > Other features like GBM_BO_IMPORT_FD_MODIFIER support are nice to<br>
> have but not a hard requirement of atomic modesetting support.<br>
> ><br>
> > What do you think ?<br>
><br>
> It's a reasonable idea, but in practice the two aren't completely<br>
> independent. The reason GBM_BO_IMPORT_FD_MODIFIER was tied up with<br>
> this is that it relies quite heavily on changes made to drm_fb which<br>
> have now been merged, but were previously part of the atomic series.<br>
> I've been considering pulling those out separately, but on the other<br>
> hand there are quite large conflicts doing so: before the 'helper'<br>
> commits, there are two separate GBM import paths for primary/scanout<br>
> and overlay planes, which only get unified inside the atomic series.<br>
><br>
> My current thinking is:<br>
> * everything up to 'atomic modesetting support' is qutie<br>
> self-contained, largely reviewed, and should hopefully be very very<br>
> close to landing by the time I can send out a new revision next week<br>
> (been busy with internal stuff & travel recently)<br>
> * once that's landed, everything up to 'Add modifiers to GBM dmabuf<br>
> import', and possibly including 'Support plane IN_FORMATS' + 'Support<br>
> modifiers with GBM' can be considered as one independent series<br>
> (though will need a non-trivial rebase) which should be quite easy to<br>
> review<br>
> * the rest of the code dealing with plane assignments (up to 'Enable<br>
> planes for atomic') can be considered another separate series; though<br>
> there are a couple of bugfixes in there, the rest is more complex and<br>
> difficult<br>
><br>
> I think it makes the most sense to work through like that in order. Of<br>
> course if you have any other ideas or priorities, I'd be really<br>
> interested to hear - anything which makes it easier to review is<br>
> obviously good! :)<br>
><br>
> Cheers,<br>
> Daniel<br>
______________________________<wbr>_________________<br>
wayland-devel mailing list<br>
<a href="mailto:wayland-devel@lists.freedesktop.org">wayland-devel@lists.<wbr>freedesktop.org</a><br>
<a href="https://lists.freedesktop.org/mailman/listinfo/wayland-devel" rel="noreferrer" target="_blank">https://lists.freedesktop.org/<wbr>mailman/listinfo/wayland-devel</a><br>
</div></div></blockquote></div><br></div>