Re: [PATCH 1/1] fbdev/hyperv_fb: Fix logic error for Gen2 VMs in hvfb_getmem()

On Wed, Jan 31, 2024 at 10:00:22PM -0800, mhkelle...@gmail.com wrote: > From: Michael Kelley > > A recent commit removing the use of screen_info introduced a logic > error. The error causes hvfb_getmem() to always return -ENOMEM > for Generation 2 VMs. As a result, the Hyper-V frame buffer >

Re: [PATCH] drm: Check output polling initialized before disabling

On Thu, Jan 04, 2024 at 09:19:42PM -0800, Shradha Gupta wrote: > On Wed, Dec 27, 2023 at 02:33:17AM -0800, Saurabh Singh Sengar wrote: > > On Tue, Dec 26, 2023 at 11:27:15PM -0800, Shradha Gupta wrote: > > > In drm_mode_config_helper_suspend() check if output polling > >

Re: [PATCH] drm: Check output polling initialized before disabling

On Tue, Dec 26, 2023 at 11:27:15PM -0800, Shradha Gupta wrote: > In drm_mode_config_helper_suspend() check if output polling > support is initialized before enabling/disabling polling. > For drivers like hyperv-drm, that do not initialize connector > polling, if suspend is called without this

Re: [PATCH] drm/hyperv: Don't rely on screen_info.lfb_base for Gen1 VMs

On Mon, Sep 12, 2022 at 09:03:53AM +0200, Thomas Zimmermann wrote: > Hi > > Am 11.09.22 um 18:21 schrieb Saurabh Singh Sengar: > >On Sat, Sep 10, 2022 at 08:11:24PM +0200, Thomas Zimmermann wrote: > >>Hi > >> > >>Am 09.09.22 um 16:43 schrieb Saurabh Seng

Re: [PATCH] drm/hyperv: Don't rely on screen_info.lfb_base for Gen1 VMs

On Sat, Sep 10, 2022 at 08:11:24PM +0200, Thomas Zimmermann wrote: > Hi > > Am 09.09.22 um 16:43 schrieb Saurabh Sengar: > >hyperv_setup_vram tries to remove conflicting framebuffer based on > >'screen_info'. As observed in past due to some bug or wrong setting > >in grub, the 'screen_info'

Re: [PATCH] drm/hyperv: Add ratelimit on error message

On Sat, Sep 10, 2022 at 08:06:05PM +0200, Thomas Zimmermann wrote: > Hi > > Am 09.09.22 um 17:09 schrieb Saurabh Sengar: > >Due to a full ring buffer, the driver may be unable to send updates to > >the Hyper-V host. But outputing the error message can make the problem > >worse because console

Re: [PATCH v4] drm/hyperv: Add error message for fb size greater than allocated

On Tue, Apr 12, 2022 at 05:06:07AM +, Dexuan Cui wrote: > > From: Saurabh Sengar > > Sent: Monday, April 11, 2022 9:29 PM > > ... > > Add error message when the size of requested framebuffer is more than > > the allocated size by vmbus mmio region for framebuffer > > The line lacks a

Re: [PATCH v3] drm/hyperv: Added error message for fb size greater than allocated

On Mon, Apr 11, 2022 at 07:02:19PM +, Dexuan Cui wrote: > > From: Saurabh Singh Sengar > > Sent: Monday, April 11, 2022 12:56 AM > > > >... > > > > - if (fb->pitches[0] * fb->height > hv->fb_size) > > >

Re: [PATCH v3] drm/hyperv: Added error message for fb size greater than allocated

On Mon, Apr 11, 2022 at 06:40:38AM +, Dexuan Cui wrote: > > Subject: [PATCH v3] drm/hyperv: Added error message for fb size greater than > > allocated > > > > Added error message when the size of requested framebuffer is more than > > the allocated size by vmbus mmio region for framebuffer >

Re: [PATCH v2] drm/hyperv: Added error message for fb size greater then allocated

On Thu, Apr 07, 2022 at 09:28:53AM -0700, Deepak Rawat wrote: > On Wed, Apr 6, 2022 at 11:27 PM Saurabh Sengar > wrote: > > > > Added error message when the size of requested framebuffer is more then > > the allocated size by vmbus mmio region for framebuffer > > > > Signed-off-by: Saurabh Sengar