On Wed, Aug 10, 2022 at 11:39:39AM -0400, Alex Deucher wrote:
> On Wed, Aug 10, 2022 at 11:38 AM Greg KH wrote:
> >
> > On Wed, Aug 10, 2022 at 11:28:18AM -0400, Alex Deucher wrote:
> > > On Tue, Jul 19, 2022 at 2:57 PM Alex Deucher
> > > wrote:
> > > >
> > > > The new vkms virtual display code
On Wed, Aug 10, 2022 at 11:28:18AM -0400, Alex Deucher wrote:
> On Tue, Jul 19, 2022 at 2:57 PM Alex Deucher
> wrote:
> >
> > The new vkms virtual display code is atomic so there is
> > no need to call drm_helper_disable_unused_functions()
> > when it is enabled. Doing so can result in a segfaul
On Wed, Aug 10, 2022 at 11:38 AM Greg KH wrote:
>
> On Wed, Aug 10, 2022 at 11:28:18AM -0400, Alex Deucher wrote:
> > On Tue, Jul 19, 2022 at 2:57 PM Alex Deucher
> > wrote:
> > >
> > > The new vkms virtual display code is atomic so there is
> > > no need to call drm_helper_disable_unused_functi
On Tue, Jul 19, 2022 at 2:57 PM Alex Deucher wrote:
>
> The new vkms virtual display code is atomic so there is
> no need to call drm_helper_disable_unused_functions()
> when it is enabled. Doing so can result in a segfault.
> When the driver switched from the old virtual display code
> to the ne