+ Dave Airlie (The DRM subsystem maintainer) for FYI Quoting Dunajski, Bartosz (2018-06-21 10:31:57) > I would like to add few things that were mentioned previously. > > According to adoption plan. > Our plan is to drop dependency on LLVM 4.0.1 (with custom patches) and instead compile with unpatched (either system or vanilla) LLVM 6.0. Work to transition our compiler stack to LLVM 6 is expected to complete in late Q3. Additionally, we are refactoring our packaging, so instead of a single neo package with multiple components we will have multiple versioned packages with clear dependencies. > > We are coordinating with ClearLinux team to get included once that happens and plan to reach out to other OSVs to do the same. > > Is this plan enough to consider NEO an actual opensource client for the coherency control patch ? Yes, once you follow through with the plan, there should be no issues about merging patches to support the driver. You may want to squeeze your timeline to be complete before 4.19-rc5, which is the feature cutoff date for 4.20, but that is rather an ambitious goal. Your original schedule would land the patches before 4.20-rc5 resulting in inclusion to 4.21. Regards, Joonas PS. I'm going on a vacation for a couple of weeks. > > PR for patch usage: > https://github.com/intel/compute-runtime/pull/53 > > Bartosz _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
