Re: [Intel-gfx] [PATCH 1/1] drm/i915: Avoid initializing framebuffer without pipes

Quoting Jani Nikula (2018-10-22 15:09:06) > On Fri, 19 Oct 2018, Chris Wilson wrote: > > Quoting Mika Kuoppala (2018-10-19 13:30:37) > >> If we try to initialize a framebuffer without pipes, we get oops > >> as we fail to get valid crtc for a PIPE A, on trying to find > >> pitch limits. This is

Re: [Intel-gfx] [PATCH 1/1] drm/i915: Avoid initializing framebuffer without pipes

On Fri, 19 Oct 2018, Chris Wilson wrote: > Quoting Mika Kuoppala (2018-10-19 13:30:37) >> If we try to initialize a framebuffer without pipes, we get oops >> as we fail to get valid crtc for a PIPE A, on trying to find >> pitch limits. This is easily demonstrated by trying to init >> framebuffer

Re: [Intel-gfx] [PATCH 1/1] drm/i915: Avoid initializing framebuffer without pipes

Quoting Mika Kuoppala (2018-10-19 13:30:37) > If we try to initialize a framebuffer without pipes, we get oops > as we fail to get valid crtc for a PIPE A, on trying to find > pitch limits. This is easily demonstrated by trying to init > framebuffer with displays disabled by

[Intel-gfx] [PATCH 1/1] drm/i915: Avoid initializing framebuffer without pipes

If we try to initialize a framebuffer without pipes, we get oops as we fail to get valid crtc for a PIPE A, on trying to find pitch limits. This is easily demonstrated by trying to init framebuffer with displays disabled by 'i915.disable_display=1' kernel cmdline. Fix this by omitting framebuffer