Date: Tue, 27 Sep 2016 13:40:56 +0300 From: abi <abi@abinet.ru> To: freebsd-x11@freebsd.org Subject: Re: gfx-next future in ports ( was gfx-next update: drm-4.8-rc2 tagged in drm-next ) Message-ID: <d4712f3f-e005-17dd-1a07-ba49b059e61c@abinet.ru> In-Reply-To: <CAPS9%2BSsKJ%2B3DBqakH1vFfM2wVWUdfr=J=W9_Ra6b%2BvzLaWv0bg@mail.gmail.com> References: <CAPS9%2BSsKJ%2B3DBqakH1vFfM2wVWUdfr=J=W9_Ra6b%2BvzLaWv0bg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Yeah, brightness and resume issues are bad enough, however both of them are on Github bug tracker, so I hope they will be eventually tracked and squashed :) On 27.09.16 09:57, Andreas Nilsson wrote: > Hello, > > first, thanks for the amazing work Matthew and everyone else! > > > > Eventually all the requisite patches to sys will make it in at which > > > point drm-next-<n> will become available as a port allowing one to > > > install the drivers just as one installs xorg and the ddx today. > > > Keeping it as a port will allow us to decouple freebsd releases from > > > graphics developments making it possible to support the latest > > > hardware on near EOL branches. > > Does this mean that all kms-enabled drivers will be removed from the main > tree and shipped as ports, or will the ports modules have higher priority > and be loaded before the ones included in GENERIC? > > I met quite a few people at EuroBSDcon running drm-next-4.7 on recent intel > cpuswith great success. The only lacking bits seems to be brightness > adjustment and suspend2ram ( screen remains off ). Is there anybody to > nudge/sponsor to have those areas looked into? > > Best regards > Andreas > _______________________________________________ > freebsd-x11@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d4712f3f-e005-17dd-1a07-ba49b059e61c>