Date: Sat, 25 Aug 2018 07:55:19 +0800 From: blubee blubeeme <gurenchan@gmail.com> To: kris@ixsystems.com Cc: FreeBSD current <freebsd-current@freebsd.org> Subject: Re: drm / drm2 removal in 12 Message-ID: <CALM2mE=mu54cQv8XCV05u2FcK0OQb4pOZOALaU46yi=0QLytrQ@mail.gmail.com> In-Reply-To: <b5159da6-c3e5-f0f2-4f53-f4dc5395d695@ixsystems.com> 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> <b5159da6-c3e5-f0f2-4f53-f4dc5395d695@ixsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Aug 25, 2018 at 7:43 AM Kris Moore <kris@ixsystems.com> wrote: > On 8/24/18 7:07 PM, blubee blubeeme wrote: > > On Sat, Aug 25, 2018 at 6:26 AM Warner Losh <imp@bsdimp.com> wrote: > > > >> On Fri, Aug 24, 2018 at 4:20 PM Matthew Macy <mmacy@freebsd.org> wrote= : > >> > >>> On Fri, Aug 24, 2018 at 14:53 Ali <aliovx@gmail.com> wrote: > >>> > >>>> On Tue, Aug 21, 2018 at 06:54:54PM -0700, Matthew Macy wrote: > >>>>> Just in case anyone misses the change to UPDATING: > >>>>> > >>>>> 20180821: > >>>>> drm and drm2 have been removed. Users on powerpc, 32-bit > >>>> hardware, > >>>>> or with GPUs predating Radeon and i915 will need to install > >> the > >>>>> graphics/drm-legacy-kmod. All other users should be able to > >> use > >>>>> one of the LinuxKPI-based ports: graphics/drm-stable-kmod, > >>>>> graphics/drm-next-kmod, graphics/drm-devel-kmod. > >>>>> Note that this applies only to 12. > >>>> I see that The removal of drm and drm2 has been reverted on svn. Cou= ld > >>>> you please kindly share the reasons behind the re-inclusion? > >>>> > >>> > >>> I can=E2=80=99t really give the blow by blow of internal project dram= a, but the > >>> gist of it is that =E2=80=9Cbest practices=E2=80=9D (which are not ye= t actually > >> documented > >>> anywhere that I=E2=80=99ve seen) were not followed with regards to th= e > >> deprecation > >>> process. Warner and others believe that we can address the objectives > of > >>> the drm removal (improving the user experience and communicating that > >>> drm/drm2 are _completely_ unsupported apart from continuing to compil= e) > >>> through less disruptive means. > >>> > >> Just so. > >> > >> Our only continued frustration is that we were never given any guidanc= e > by > >>> RE or core on said =E2=80=9Cbest practices=E2=80=9D when the discussi= on was taking > place > >> in > >>> May and then those groups behaved as if this were a surprise when the > >>> removal happened. I=E2=80=99m cautiously optimistic that this well ex= pedite > >>> improving communications on those matters. > >>> > >> All the problems that are exposed by this aren't technical. This one i= s > >> social, but no less important. > >> > >> Warner > >> _______________________________________________ > >> freebsd-current@freebsd.org mailing list > >> https://lists.freebsd.org/mailman/listinfo/freebsd-current > >> To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > >> > > I've been watching this debacle for quite some time now and I'd just li= ke > > to ask why the rush? > > > > The graphics team is working very hard to destroy the stability of > FreeBSD > > just so that they can force their uncooked work down users throats. > > > > The Linuxkpi is unstable at best, alpha level software that's constantl= y > in > > need of someone to go and fix something on FreeBSD because Linux devs > > decided to make some changes or implement a new feature. > > > > This project: https://wiki.freebsd.org/Use%20linuxkpi%20in%20DRM > > Goals > > > > - Move DRM headers to a similar location as Linux > > - > > > > Use kmalloc() instead of malloc(9) > > - Use kref > > - > > > > Use idr and get rid of drm_gem_names.c > > - Use PCI API > > - Use Linux locking primitives > > > > is garbage, if you want to use develop Linux code and use Linux then go > do > > that on Linux. > > > > Are these guys insane and please avoid the nonsense about you're doing > this > > in your spare time. > > > > If you cannot devote the resources to do something right then don't do = it > > at all. > > > > Keep that stuff in to yourself or anyone crazy enough to follow those > steps > > to get it up and running, you guys cannot expect to contaminate the > entire > > FreeBSD project for this mess. > > > > This is nonsense and I hope that more people who see it as such would s= ay > > so and stop having these guys forcing this crap; it's maintenance hell > who > > will maintain it if they decide to leave? > > > > Best, > > Owen > > _______________________________________________ > > freebsd-current@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-current > > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org" > > I've been personally using the new DRM bits since almost day one. I > haven't found it to be unstable in the slightest. Compared to not having > it and being forced to run 5+ year old hardware, it's been a huge > blessing for those of us who care about running FreeBSD as a modern > desktop / laptop. > > FreeBSD being an open source project, you are welcome to contribute back > your work anytime. But since I don't imagine we'll see that patch coming > anytime soon, I'll stick with this new LinuxKPI-powered, Plasma-desktop > running awesomeness. > > (Written from my brand new Lenovo P71 which worked flawlessly out of box) > > > -- > Kris Moore > Vice President of Engineering > iXsystems > Enterprise Storage & Servers Driven By Open Source > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org= " > Please tell me more about you're modern hardware, Kris Vice President of Engineering at iXsystems. Try asking a person who doesn't run server infrastructure software and hardware to get that stuff up and running, would you? ----- pciconf -lv hostb0@pci0:0:0:0: class=3D0x060000 card=3D0x6a011558 chip=3D0x19108086 rev= =3D0x07 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers' class =3D bridge subclass =3D HOST-PCI pcib1@pci0:0:1:0: class=3D0x060400 card=3D0x6a011558 chip=3D0x19018086 rev= =3D0x07 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D 'Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16)' class =3D bridge subclass =3D PCI-PCI xhci0@pci0:0:20:0: class=3D0x0c0330 card=3D0x6a011558 chip=3D0xa12f8086 rev= =3D0x31 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Sunrise Point-H USB 3.0 xHCI Controller' class =3D serial bus subclass =3D USB none0@pci0:0:22:0: class=3D0x078000 card=3D0x6a011558 chip=3D0xa13a8086 rev= =3D0x31 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Sunrise Point-H CSME HECI' class =3D simple comms ahci0@pci0:0:23:0: class=3D0x010601 card=3D0x6a011558 chip=3D0xa1038086 rev= =3D0x31 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Sunrise Point-H SATA Controller [AHCI mode]' class =3D mass storage subclass =3D SATA pcib2@pci0:0:28:0: class=3D0x060400 card=3D0x6a011558 chip=3D0xa1108086 rev= =3D0xf1 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D 'Sunrise Point-H PCI Express Root Port' class =3D bridge subclass =3D PCI-PCI pcib3@pci0:0:28:4: class=3D0x060400 card=3D0x6a011558 chip=3D0xa1148086 rev= =3D0xf1 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D 'Sunrise Point-H PCI Express Root Port' class =3D bridge subclass =3D PCI-PCI pcib4@pci0:0:28:6: class=3D0x060400 card=3D0x6a011558 chip=3D0xa1168086 rev= =3D0xf1 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D 'Sunrise Point-H PCI Express Root Port' class =3D bridge subclass =3D PCI-PCI pcib5@pci0:0:29:0: class=3D0x060400 card=3D0x6a011558 chip=3D0xa1188086 rev= =3D0xf1 hdr=3D0x01 vendor =3D 'Intel Corporation' device =3D 'Sunrise Point-H PCI Express Root Port' class =3D bridge subclass =3D PCI-PCI isab0@pci0:0:31:0: class=3D0x060100 card=3D0x6a011558 chip=3D0xa14e8086 rev= =3D0x31 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Sunrise Point-H LPC Controller' class =3D bridge subclass =3D PCI-ISA none1@pci0:0:31:2: class=3D0x058000 card=3D0x6a011558 chip=3D0xa1218086 rev= =3D0x31 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Sunrise Point-H PMC' class =3D memory hdac0@pci0:0:31:3: class=3D0x040300 card=3D0x6a021558 chip=3D0xa1708086 rev= =3D0x31 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Sunrise Point-H HD Audio' class =3D multimedia subclass =3D HDA none2@pci0:0:31:4: class=3D0x0c0500 card=3D0x6a011558 chip=3D0xa1238086 rev= =3D0x31 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Sunrise Point-H SMBus' class =3D serial bus subclass =3D SMBus vgapci0@pci0:1:0:0: class=3D0x030000 card=3D0x6a021558 chip=3D0x1ba110de re= v=3D0xa1 hdr=3D0x00 vendor =3D 'NVIDIA Corporation' device =3D 'GP104M [GeForce GTX 1070 Mobile]' class =3D display subclass =3D VGA none3@pci0:109:0:0: class=3D0xff0000 card=3D0x6a011558 chip=3D0x528710ec re= v=3D0x01 hdr=3D0x00 vendor =3D 'Realtek Semiconductor Co., Ltd.' device =3D 'RTL8411B PCI Express Card Reader' re0@pci0:109:0:1: class=3D0x020000 card=3D0x6a011558 chip=3D0x816810ec rev= =3D0x12 hdr=3D0x00 vendor =3D 'Realtek Semiconductor Co., Ltd.' device =3D 'RTL8111/8168/8411 PCI Express Gigabit Ethernet Controll= er' class =3D network subclass =3D ethernet iwm0@pci0:110:0:0: class=3D0x028000 card=3D0x50108086 chip=3D0x095a8086 rev= =3D0x48 hdr=3D0x00 vendor =3D 'Intel Corporation' device =3D 'Wireless 7265' class =3D network nvme0@pci0:111:0:0: class=3D0x010802 card=3D0x390a8086 chip=3D0xf1a58086 re= v=3D0x03 hdr=3D0x00 vendor =3D 'Intel Corporation' class =3D mass storage subclass =3D NVM
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CALM2mE=mu54cQv8XCV05u2FcK0OQb4pOZOALaU46yi=0QLytrQ>