Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 21 May 2018 15:49:27 -0700
From:      Steve Kargl <sgk@troutmask.apl.washington.edu>
To:        "K. Macy" <kmacy@freebsd.org>
Cc:        Rozhuk Ivan <rozhuk.im@gmail.com>, Oliver Pinter <oliver.pinter@hardenedbsd.org>, Niclas Zeising <zeising+freebsd@daemonic.se>, Warner Losh <imp@bsdimp.com>, FreeBSD X11 mailing list <freebsd-x11@freebsd.org>, Current FreeBSD <freebsd-current@freebsd.org>
Subject:   Re: [RFC] Deprecation and removal of the drm2 driver
Message-ID:  <20180521224927.GA9925@troutmask.apl.washington.edu>
In-Reply-To: <CAHM0Q_ND3_4EB7mXoPK94wQSXsrgpvLO8D2kRDMnA=pZ4wLzUA@mail.gmail.com>
References:  <CAPS9%2BSv6SDWkbrEZruM4g2%2BOfw4ksvbtiMF=Q_towrMtJrgt1w@mail.gmail.com> <20180518193009.GA88432@troutmask.apl.washington.edu> <CANCZdfoMrFCyPteChSWgfYRY-uOyazzR0ZbYvp_OVmXRTe-Hqw@mail.gmail.com> <20180520164011.GA6276@troutmask.apl.washington.edu> <88843bfb-34de-382c-9409-83f9ad54c8c4@daemonic.se> <CAPQ4ffvd1da%2BiMXtPfz%2BxETqPZwgmNoBa5yZMSF26qPMkSD2qQ@mail.gmail.com> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> <20180522011543.3f621882@gmail.com> <CAHM0Q_ND3_4EB7mXoPK94wQSXsrgpvLO8D2kRDMnA=pZ4wLzUA@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 21, 2018 at 03:20:49PM -0700, K. Macy wrote:
> >
> > I just ask.
> > Or why not include drm-next to base svn repo and add some
> > option to make.conf to swith drm2/dem-next ?
> 
> Even if it's not being built on amd64 we're still responsible for
> keeping it building on !amd64 so long as it's in base. This makes
> changing APIs and universe runs more burdensome. The graphics
> developers have given you notice that it will now be your collective
> responsibility to keep it up to date.
> 

Not quite.  One graphics developer has indicated a desire 
to remove working code, because it interferes with the
graphics developers' port on a single architecture.  There
is no indication by that graphics developer that drm2 will
be available in ports.  You can go read the original post
here:

https://lists.freebsd.org/pipermail/freebsd-current/2018-May/069401.html

The last paragraph is

   What does the community think?  Is there anyone still using
   the drm2 driver on 12-CURRENT?  If so, what is preventing
   you from switching to the port?
 
The answer to the last two questions are "yes" and "the port
does not work on i386".

Yes, I recognize that you're clever enough to purposefully
break the API so that you can thumb your nose at those of
us who have older hardware.

What is wrong with using 

.if ${MACHINE_ARCH} != amd64
...
.endif

to enable/disable drm2?

-- 
Steve



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180521224927.GA9925>