From: Wei Liu Sent: Friday, March 1, 2024 1:26 AM
>
> On Fri, Feb 09, 2024 at 04:53:37PM +0100, Helge Deller wrote:
> > On 2/9/24 16:23, Michael Kelley wrote:
> > > From: Thomas Zimmermann Sent: Thursday, February 1,
> > > 2024 12:17 AM
> [...]
> > >
> > > Wei Liu and Helge Deller --
> > >
> >
On Fri, Feb 09, 2024 at 04:53:37PM +0100, Helge Deller wrote:
> On 2/9/24 16:23, Michael Kelley wrote:
> > From: Thomas Zimmermann Sent: Thursday, February 1,
> > 2024 12:17 AM
[...]
> >
> > Wei Liu and Helge Deller --
> >
> > Should this fix go through the Hyper-V tree or the fbdev tree? I'm
On 2/9/24 16:23, Michael Kelley wrote:
From: Thomas Zimmermann Sent: Thursday, February 1, 2024
12:17 AM
Hi
Am 01.02.24 um 07:00 schrieb mhkelle...@gmail.com:
From: Michael Kelley
A recent commit removing the use of screen_info introduced a logic
error. The error causes hvfb_getmem() to a
From: Thomas Zimmermann Sent: Thursday, February 1, 2024
12:17 AM
>
> Hi
>
> Am 01.02.24 um 07:00 schrieb mhkelle...@gmail.com:
> > 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
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
> devi
Hi
Am 01.02.24 um 07:00 schrieb mhkelle...@gmail.com:
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
device fails to initialize. T
