Date: Sun, 26 Aug 2018 18:41:48 +0800 From: blubee blubeeme <gurenchan@gmail.com> To: Hans Petter Selasky <hps@selasky.org> Cc: pmcnary@cameron.net, Johannes Lundberg <johalun0@gmail.com>, freebsd-stable@freebsd.org, mmacy@freebsd.org, Ali Abdallah <aliovx@gmail.com>, FreeBSD current <freebsd-current@freebsd.org>, =?UTF-8?Q?Dag=2DErling_Sm=C3=B8rgrav?= <des@des.no> Subject: Re: drm / drm2 removal in 12 Message-ID: <CALM2mE=z-WcEJQnkmoS8k6V5YKLk-DORcFQGjTPJ8qULTF%2B3FQ@mail.gmail.com> In-Reply-To: <cdc72a29-745b-939e-a5ac-dc3693fa6b42@selasky.org> References: <CAPrugNr9wN63ANjTYzyrHRegr9KTk_OSTLfrt%2BhktCnfKX=_mg@mail.gmail.com> <20180824215302.ivfna55jtrtc5trg@freebsd480.station> <CAPrugNqV6k2QTuiLerAKLB_hV1hkZNi4MLNqKU7MtVnMhMfPQw@mail.gmail.com> <CANCZdfp2rf=5e-qTV=-4yFrLPugn0UhtYovXdesJWbRWAjdGTg@mail.gmail.com> <CALM2mEmJVqfeERTL4AWw7cY3YfPUY6TFw==1hzBqsDJNDde_Uw@mail.gmail.com> <CAPrugNqsqQds6tBzeQcA%2B5tD4xh%2Bi1Fef2ta8Qjf5E6LTxPq4Q@mail.gmail.com> <CALM2mEmyjKD5vQexvHfeZK0Jud7HpGSn3RspBqFq49TzrfcwNg@mail.gmail.com> <86k1oepbdr.fsf@next.des.no> <CALM2mE=T_uEVPVi7J%2BjA-8c89T46%2B9X5wk1Xo5C8EfQmKap9yw@mail.gmail.com> <CAECmPwuX31et58uQ%2BryY0sugBTFsHTr-Rynm0jy67siz=J5SzQ@mail.gmail.com> <CALM2mE=tL5mTA4PPjYXmxdgeZbZBJDPUqXkAC5LEo3QcwYF3CQ@mail.gmail.com> <180f8f99-5fa1-1411-59e6-856e3ebc370c@cameron.net> <CALM2mE=h-=0dPht02xQ86K%2BKypcVTB4ThUuB6LMQE%2BaUWcrtww@mail.gmail.com> <cdc72a29-745b-939e-a5ac-dc3693fa6b42@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Aug 26, 2018 at 4:32 PM Hans Petter Selasky <hps@selasky.org> wrote: > On 8/26/18 3:20 AM, blubee blubeeme wrote: > > Have you or anyone working on this drm-legacy-kmod stuff done any > testings > > of how this will affect current users? > > Hi Blubee, > > Are you here to try to stir a conflict? > If so that is not appreciated. > > --HPS > Hans, you of all people should know that's not true. I would think that trying to sneak in code during a code freeze that would break the release. Forcing the core devs to revert those changes and having to dust off old policies to try to keep you guys in check is what's stirring up conflicts, but hey; what do I know? It's really sad state when capable engineers are so obsessed with something that they cannot see the forest for the trees. Try to step away from the canvas and look at the big picture. If you don't mind me asking, Hans care to answer these questions below? 1) Take a [test] system with the current graphics stack installed and working. 2) Apply your patches to remove the drm from base to create a port 3) update the working [test] system after applying your changes How does your changes affect a [test] system that is already up and running? Have any of you guys tried that? Do you have any documentation on how it'll affect users. You guys want to remove things from the current system but you come with; it works for us hobbyists. Where do users go to get steps to do all of this stuff? You've repeatedly said what you want to do sure, but have you tested it?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALM2mE=z-WcEJQnkmoS8k6V5YKLk-DORcFQGjTPJ8qULTF%2B3FQ>