Re: [PATCH 01/43] drm/fbdev-generic: Do not set physical framebuffer address

Maxime Ripard writes: > On Mon, Mar 18, 2024 at 08:59:01AM +0100, Thomas Zimmermann wrote: >> Hi >> >> Am 18.03.24 um 03:35 schrieb Zack Rusin: >> > On Tue, Mar 12, 2024 at 11:48 AM Thomas Zimmermann >> > wrote: >> > > Framebuffer memory is allocated via vmalloc() from non-contiguous >> > > ph

Re: [PATCH 01/43] drm/fbdev-generic: Do not set physical framebuffer address

On Mon, Mar 18, 2024 at 08:59:01AM +0100, Thomas Zimmermann wrote: > Hi > > Am 18.03.24 um 03:35 schrieb Zack Rusin: > > On Tue, Mar 12, 2024 at 11:48 AM Thomas Zimmermann > > wrote: > > > Framebuffer memory is allocated via vmalloc() from non-contiguous > > > physical pages. The physical frameb

Re: [PATCH 01/43] drm/fbdev-generic: Do not set physical framebuffer address

Hi Am 17.03.24 um 13:43 schrieb Javier Martinez Canillas: Thomas Zimmermann writes: Hello Thomas, Framebuffer memory is allocated via vmalloc() from non-contiguous It's vmalloc() true, but through vzmalloc() so I would mention that function instead in the commit message. Ok. physical

Re: [PATCH 01/43] drm/fbdev-generic: Do not set physical framebuffer address

Hi Am 18.03.24 um 03:35 schrieb Zack Rusin: On Tue, Mar 12, 2024 at 11:48 AM Thomas Zimmermann wrote: Framebuffer memory is allocated via vmalloc() from non-contiguous physical pages. The physical framebuffer start address is therefore meaningless. Do not set it. The value is not used within

Re: [PATCH 01/43] drm/fbdev-generic: Do not set physical framebuffer address

On Tue, Mar 12, 2024 at 11:48 AM Thomas Zimmermann wrote: > > Framebuffer memory is allocated via vmalloc() from non-contiguous > physical pages. The physical framebuffer start address is therefore > meaningless. Do not set it. > > The value is not used within the kernel and only exported to users

Re: [PATCH 01/43] drm/fbdev-generic: Do not set physical framebuffer address

Thomas Zimmermann writes: Hello Thomas, > Framebuffer memory is allocated via vmalloc() from non-contiguous It's vmalloc() true, but through vzmalloc() so I would mention that function instead in the commit message. > physical pages. The physical framebuffer start address is therefore > meanin