Date: Tue, 22 May 2018 16:49:19 -0500 From: "A. Wilcox" <AWilcox@Wilcox-Tech.com> To: freebsd-current@freebsd.org Subject: Re: [RFC] Deprecation and removal of the drm2 driver Message-ID: <1db36614-5381-dac6-f754-d828cee2a743@Wilcox-Tech.com> In-Reply-To: <CAPS9%2BSt5dZaAwC%2Bw1EyXW2hr4D4dgpZUzVjQ2=aKdMS9ucZaRg@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> <20180521224927.GA9925@troutmask.apl.washington.edu> <CAECmPwsfSSYtcHypWej4vTiDJy_wHM0pm8YchZniAe17ojXGgA@mail.gmail.com> <CAPS9%2BSt5dZaAwC%2Bw1EyXW2hr4D4dgpZUzVjQ2=aKdMS9ucZaRg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --1jk0xfrflS9rqZlVI6xiWoSospKv7F9CC Content-Type: multipart/mixed; boundary="jOZK6GUcvw6EFXup9vpQ9FaToQMpsrQwP"; protected-headers="v1" From: "A. Wilcox" <AWilcox@Wilcox-Tech.com> To: freebsd-current@freebsd.org Message-ID: <1db36614-5381-dac6-f754-d828cee2a743@Wilcox-Tech.com> Subject: Re: [RFC] Deprecation and removal of the drm2 driver References: <CAPS9+Sv6SDWkbrEZruM4g2+Ofw4ksvbtiMF=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+iMXtPfz+xETqPZwgmNoBa5yZMSF26qPMkSD2qQ@mail.gmail.com> <20180521024050.0857a787@gmail.com> <20180521170728.GA14025@troutmask.apl.washington.edu> <20180522011543.3f621882@gmail.com> <CAHM0Q_ND3_4EB7mXoPK94wQSXsrgpvLO8D2kRDMnA=pZ4wLzUA@mail.gmail.com> <20180521224927.GA9925@troutmask.apl.washington.edu> <CAECmPwsfSSYtcHypWej4vTiDJy_wHM0pm8YchZniAe17ojXGgA@mail.gmail.com> <CAPS9+St5dZaAwC+w1EyXW2hr4D4dgpZUzVjQ2=aKdMS9ucZaRg@mail.gmail.com> In-Reply-To: <CAPS9+St5dZaAwC+w1EyXW2hr4D4dgpZUzVjQ2=aKdMS9ucZaRg@mail.gmail.com> --jOZK6GUcvw6EFXup9vpQ9FaToQMpsrQwP Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: quoted-printable >>>>> 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.h= tml >>> >>> 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} !=3D amd64 >>> ... >>> .endif >>> >>> to enable/disable drm2? >=20 > With such long-time support offered by 11- branch, why hamper developme= nt > of 12 by lugging around old, hard to maintain code that is relevant for= > only legacy hardware? >=20 it makes me giggle that people still think non-amd64 is "legacy". i386 is alive and well - new chips are being fabbed based on the 586 design with pci-e slots; not to mention things like the Talos and AmigaOne for PowerPC. --arw --=20 A. Wilcox (awilfox) Open-source programmer (C, C++, Python) https://code.foxkit.us/u/awilfox/ --jOZK6GUcvw6EFXup9vpQ9FaToQMpsrQwP-- --1jk0xfrflS9rqZlVI6xiWoSospKv7F9CC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEjNyWOYPU1SaTSMHHyynLUZIrnRQFAlsEkF8ACgkQyynLUZIr nRQzBRAAqqcbCiOTfahzcXLwcv0iiEjTyAo9qItXI8fQRxQDJNGTF5NwVkdBbQ19 4WjsGRg7hvvV8D3jH5XTfnM8IWJbKiSi6M+Kxw12pkbxFdf5bknGnNkMI7bv5HkH MowXf6+0+Bi0lbrOTBJSktOIGt5W5cBZbGroCzUrnsFrpE/JYMTVPghuteQm0+b4 Fhtw2DYSRBxocAuC9zUHQLsT6CTq5JDhcQxKd46niXjztAMH4rU6z6Y1ftjBjhHk 34EOjJL4Vt/+S8CqgdmU19Kuh6hN1T57H3zDEjpBfjXIJ96sGbDNudiWrFJebg3L 2Ws+vIrVNq/MvsSxn4Gv1aMbHle+UedsNFbe1fv/mDY2OXjyksvaXN1NDRodAHvW R/KGCfeGaZhgWFGYt9N/H0IhF8/pd2Qrpa4LsYlJo9AGaK3g6Sc0sQdMHR3X2LSL W5B03BKVX9t07qL1w0mHzS4umk2Zx5JkHixxSgaBlGk0Mrv1AeV6WDFBkR/YzZSY OnVPbsSIl/UzpIF3TXMmf7Q0tgmJihP5vlBSFWI7MpgtEIfL9RUB9Qy8wA43zSXh 6l/y/aIBReJ4sUWiG/5J+6HsqSVLSOwwlJn1x+ouO7cWiy2xtOAd0WlI3EqCL0Xh xwsbKhnpxKz0bEK/a8u6kkDHPf/sqOBINYIZOvsVhtsCBg0JO+c= =bHE3 -----END PGP SIGNATURE----- --1jk0xfrflS9rqZlVI6xiWoSospKv7F9CC--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1db36614-5381-dac6-f754-d828cee2a743>