svn commit: r338172 - Now deprecating DRM

[Kevin Bowling]

On Thu, Aug 23, 2018 at 10:55 AM, Rodney W. Grimes
<freebsd at pdx.rh.cn85.dnsmgr.net> wrote:
> [ Charset UTF-8 unsupported, converting... ]
>> On Wed, Aug 22, 2018 at 10:08 AM Rodney W. Grimes <
>> freebsd at pdx.rh.cn85.dnsmgr.net> wrote:
>>
>> > I think this deprecation is a rather serious deviation
>> > from the stated policy, in that 0 notification was
>> > made, core IMHO, has overstepped some boundaries in
>> > that respect.   These policies are promises to the
>> > downstream consumers, and violating them is very
>> > poor planning.
>> >
>>
>> Despite what the commit said, core didn't actually formally approve it
>> before the fact. That was one of the many miscommunications surrounding
>> this episode.
>
> Well I would say inlight of that fact a revert should be a no questions
> asked, doing much else risks build breakage within hours of code freeze.
>
>
>> I don't think you'll find anybody who would say this was well planned or
>> well executed.
>
> Agreed, so lets be simple in correcting it?

This is feeding more unnecessary inflammation.  I disagree with this
statement and so do a lot of other people including multiple on core.
There is certainly an opportunity to do better, but the policy and
procedures being spoken are not installed yet, we're under hard
deadline to lock down the 12.x ABI and the proposed review for a
tegra124-private drm2 addresses all who have standing in the matter.

Matt Joras offered a very professional and rational take on things on
developers at .  I would encourage people to noodle on that before
continuing to inflame the issues.

> From some investigation even the claim that "in base drm conflicts with
> ports drm" is not totally true, you just have to take a few steps to
> be sure you do not load the base versions, and do load the ports version.

It does.  The graphics team unilaterally agrees.