[PATCH 2/2] drm: make DRI1 drivers depend on BROKEN
Emil Velikov
emil.l.velikov at gmail.com
Fri Aug 26 01:23:13 UTC 2016
Hi Kevin,
On 26 August 2016 at 01:19, Kevin Brace <kevinbrace at gmx.com> wrote:
> I do not want to be seen as stopping progress, but there are still people who use less than current hardware (myself and countless others) or non Big 3 x86 graphics (NVIDIA, AMD, and Intel) for things like thin clients.
[snip]
> Anyway, regarding the move to DRI2 / KMS so that DRI1 can be discontinued, I am not personally against it in the long run, but the work on it has stalled.
>
Afaict nobody is discontinuing DRI1, but marking it as BROKEN. Why you
may ask - simply because there has been virtually zero development
effort (general refactoring do not count) and serious testing, for
those drivers over the last 5+ years.
FWIW I would strongly recommend leaving UMS at peace and working
towards KMS. Having a hybrid UMS/KMS stack is possible, but it's far
too picky and time consuming even for larger teams.
On the forward porting efforts - DRM evolves rapidly so one could
consider starting from scratch. Wire up the (atomic?) mode setting
side first then think about the render side of things.
Regards,
Emil
More information about the dri-devel
mailing list