[PATCH] drm/todo: Drop todo item to request memory regions in all fbdev drivers

[PATCH] drm/todo: Drop todo item to request memory regions in all fbdev drivers

[Helge Deller]

This item is tagged for beginners, so often people not familiar with
the fbdev drivers think this is an easy task, start up their AI tools
and blindly send in the generated code as patches.

The problem:
- Those patches often introduce bugs, so
- ideally want the code tested, since ressource misconfigurations
  often lead to failing drivers
- The patches are often unnecessary, since in the old machines with the
  old graphic cards resource conflicts usually don't happen as only one
  graphic card can be used at a time anyway.
- and today most relevant drivers have necessary patches already
  implemented.

So, let's get rid of this todo item and silence the steady stream of
stupid patches.

Signed-off-by: Helge Deller <deller@gmx.de>
---
 Documentation/gpu/todo.rst | 16 ----------------
 1 file changed, 16 deletions(-)

diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst
index bc9f14c8a2ec..b4dd64a8cc06 100644
--- a/Documentation/gpu/todo.rst
+++ b/Documentation/gpu/todo.rst
@@ -448,22 +448,6 @@ Contact: Thomas Zimmermann <tzimmermann@suse.de>
 
 Level: Intermediate
 
-Request memory regions in all fbdev drivers
---------------------------------------------
-
-Old/ancient fbdev drivers do not request their memory properly.
-Go through these drivers and add code to request the memory regions
-that the driver uses. This requires adding calls to request_mem_region(),
-pci_request_region() or similar functions. Use helpers for managed cleanup
-where possible. Problematic areas include hardware that has exclusive ranges
-like VGA. VGA16fb does not request the range as it is expected.
-Drivers are pretty bad at doing this and there used to be conflicts among
-DRM and fbdev drivers. Still, it's the correct thing to do.
-
-Contact: Thomas Zimmermann <tzimmermann@suse.de>
-
-Level: Starter
-
 Remove driver dependencies on FB_DEVICE
 ---------------------------------------
 
-- 
2.53.0

Re: [PATCH] drm/todo: Drop todo item to request memory regions in all fbdev drivers

[Geert Uytterhoeven]

Hi Helge,

On Thu, 23 Apr 2026 at 23:04, Helge Deller <deller@gmx.de> wrote:
> This item is tagged for beginners, so often people not familiar with
> the fbdev drivers think this is an easy task, start up their AI tools
> and blindly send in the generated code as patches.
>
> The problem:
> - Those patches often introduce bugs, so
> - ideally want the code tested, since ressource misconfigurations

resource

>   often lead to failing drivers
> - The patches are often unnecessary, since in the old machines with the
>   old graphic cards resource conflicts usually don't happen as only one
>   graphic card can be used at a time anyway.
> - and today most relevant drivers have necessary patches already
>   implemented.
>
> So, let's get rid of this todo item and silence the steady stream of
> stupid patches.
>
> Signed-off-by: Helge Deller <deller@gmx.de>

Thanks for your patch!

> --- a/Documentation/gpu/todo.rst
> +++ b/Documentation/gpu/todo.rst
> @@ -448,22 +448,6 @@ Contact: Thomas Zimmermann <tzimmermann@suse.de>
>
>  Level: Intermediate
>
> -Request memory regions in all fbdev drivers
> ---------------------------------------------
> -
> -Old/ancient fbdev drivers do not request their memory properly.
> -Go through these drivers and add code to request the memory regions
> -that the driver uses. This requires adding calls to request_mem_region(),
> -pci_request_region() or similar functions. Use helpers for managed cleanup
> -where possible. Problematic areas include hardware that has exclusive ranges
> -like VGA. VGA16fb does not request the range as it is expected.
> -Drivers are pretty bad at doing this and there used to be conflicts among
> -DRM and fbdev drivers. Still, it's the correct thing to do.
> -
> -Contact: Thomas Zimmermann <tzimmermann@suse.de>
> -
> -Level: Starter

I am not really against keeping this item. But as the related changes
are not pure refactorings, and cause a change in behavior, they _must_
be tested on actual hardware.  I guess making that explicit would be a
bit silly (heck, all changes should be tested).  And bumping the level
to intermediate might send the wrong message, too (starters don't need
to test? Doh...)

Thomas: do we still any hardware for which there exist both DRM and
fbdev drivers, and the resource management is missing in the fbdev
drivers?

> -
>  Remove driver dependencies on FB_DEVICE
>  ---------------------------------------
>

Gr{oetje,eeting}s,

                        Geert

-- 
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

Re: [PATCH] drm/todo: Drop todo item to request memory regions in all fbdev drivers

[Thomas Zimmermann]

Hi

>> -Contact: Thomas Zimmermann <tzimmermann@suse.de>
>> -
>> -Level: Starter
> I am not really against keeping this item. But as the related changes
> are not pure refactorings, and cause a change in behavior, they _must_
> be tested on actual hardware.  I guess making that explicit would be a
> bit silly (heck, all changes should be tested).  And bumping the level
> to intermediate might send the wrong message, too (starters don't need
> to test? Doh...)
>
> Thomas: do we still any hardware for which there exist both DRM and
> fbdev drivers, and the resource management is missing in the fbdev
> drivers?

See my other reply on why this item exists. It's also about hand-over 
during boot up, which could affect any/most driver.

We can remove the item now, if that helps, but it might lead to other 
bug reports later on.

Best regards
Thomas



>
>> -
>>   Remove driver dependencies on FB_DEVICE
>>   ---------------------------------------
>>
> Gr{oetje,eeting}s,
>
>                          Geert
>

-- 
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Jochen Jaser, Andrew McDonald, Werner Knoblich, (HRB 36809, AG Nürnberg)

Re: [PATCH] drm/todo: Drop todo item to request memory regions in all fbdev drivers

[Helge Deller]

On 4/24/26 09:01, Thomas Zimmermann wrote:
> Hi
> 
>>> -Contact: Thomas Zimmermann <tzimmermann@suse.de>
>>> -
>>> -Level: Starter
>> I am not really against keeping this item. But as the related changes
>> are not pure refactorings, and cause a change in behavior, they _must_
>> be tested on actual hardware.  I guess making that explicit would be a
>> bit silly (heck, all changes should be tested).  And bumping the level
>> to intermediate might send the wrong message, too (starters don't need
>> to test? Doh...)
>>
>> Thomas: do we still any hardware for which there exist both DRM and
>> fbdev drivers, and the resource management is missing in the fbdev
>> drivers?
> 
> See my other reply on why this item exists. It's also about hand-
> over during boot up, which could affect any/most driver.
>
> We can remove the item now, if that helps, but it might lead to other bug reports later on.

Thanks, I'll remove the item now.
In case we run into reports later on, I'm happy to work with you on them then.

Can I add an Acked-by from you?

Helge

Re: [PATCH] drm/todo: Drop todo item to request memory regions in all fbdev drivers

[Thomas Zimmermann]

Hi

Am 24.04.26 um 10:36 schrieb Helge Deller:
> On 4/24/26 09:01, Thomas Zimmermann wrote:
>> Hi
>>
>>>> -Contact: Thomas Zimmermann <tzimmermann@suse.de>
>>>> -
>>>> -Level: Starter
>>> I am not really against keeping this item. But as the related changes
>>> are not pure refactorings, and cause a change in behavior, they _must_
>>> be tested on actual hardware.  I guess making that explicit would be a
>>> bit silly (heck, all changes should be tested).  And bumping the level
>>> to intermediate might send the wrong message, too (starters don't need
>>> to test? Doh...)
>>>
>>> Thomas: do we still any hardware for which there exist both DRM and
>>> fbdev drivers, and the resource management is missing in the fbdev
>>> drivers?
>>
>> See my other reply on why this item exists. It's also about hand-
>> over during boot up, which could affect any/most driver.
>>
>> We can remove the item now, if that helps, but it might lead to other 
>> bug reports later on.
>
> Thanks, I'll remove the item now.
> In case we run into reports later on, I'm happy to work with you on 
> them then.
>
> Can I add an Acked-by from you?

No. I think I made my point clear why this item exists. We can talk 
about how to handle these old drivers (staging, removal, fixing, etc), 
but pretending it's all well will not solve any issues.

Best regards
Thomas

>
> Helge

-- 
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Jochen Jaser, Andrew McDonald, Werner Knoblich, (HRB 36809, AG Nürnberg)

Re: [PATCH] drm/todo: Drop todo item to request memory regions in all fbdev drivers

[Thomas Zimmermann]

Hi

Am 23.04.26 um 22:55 schrieb Helge Deller:
> This item is tagged for beginners, so often people not familiar with
> the fbdev drivers think this is an easy task, start up their AI tools
> and blindly send in the generated code as patches.
>
> The problem:
> - Those patches often introduce bugs, so
> - ideally want the code tested, since ressource misconfigurations
>    often lead to failing drivers
> - The patches are often unnecessary, since in the old machines with the
>    old graphic cards resource conflicts usually don't happen as only one
>    graphic card can be used at a time anyway.
> - and today most relevant drivers have necessary patches already
>    implemented.
>
> So, let's get rid of this todo item and silence the steady stream of
> stupid patches.

I see that AI patches can be problematic, but reserving these regions is 
still the correct thing to do. Removing the TODO item will not change that.

Some background on why this item exists: we currently use aperture 
helpers [1] to manage ownership of the framebuffer memory during boot 
up. This is necessary to switch from the system-framebuffer driver 
(i..e, simplefb, simpledrm, etc) to the hardware's native driver. But 
this is all ad-hoc because Linux' resource management doesn't do this 
for us. Before we can integrate any such functionality, we have to fix 
all drivers to reserve their resources correctly.

If we remove the TODO item, we'd likely still want to move forward with 
improving resource management. If that breaks unfixed fbdev drivers, 
users would then also send bug reports.

And the other point is (again) that if there are no means of testing a 
driver and no information whether a driver is actually in used by 
anyone, it's maybe time to remove the driver.

[1] 
https://elixir.bootlin.com/linux/v7.0.1/source/drivers/video/aperture.c#L17

Best regards
Thomas


>
> Signed-off-by: Helge Deller <deller@gmx.de>
> ---
>   Documentation/gpu/todo.rst | 16 ----------------
>   1 file changed, 16 deletions(-)
>
> diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst
> index bc9f14c8a2ec..b4dd64a8cc06 100644
> --- a/Documentation/gpu/todo.rst
> +++ b/Documentation/gpu/todo.rst
> @@ -448,22 +448,6 @@ Contact: Thomas Zimmermann <tzimmermann@suse.de>
>   
>   Level: Intermediate
>   
> -Request memory regions in all fbdev drivers
> ---------------------------------------------
> -
> -Old/ancient fbdev drivers do not request their memory properly.
> -Go through these drivers and add code to request the memory regions
> -that the driver uses. This requires adding calls to request_mem_region(),
> -pci_request_region() or similar functions. Use helpers for managed cleanup
> -where possible. Problematic areas include hardware that has exclusive ranges
> -like VGA. VGA16fb does not request the range as it is expected.
> -Drivers are pretty bad at doing this and there used to be conflicts among
> -DRM and fbdev drivers. Still, it's the correct thing to do.
> -
> -Contact: Thomas Zimmermann <tzimmermann@suse.de>
> -
> -Level: Starter
> -
>   Remove driver dependencies on FB_DEVICE
>   ---------------------------------------
>   

-- 
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Jochen Jaser, Andrew McDonald, Werner Knoblich, (HRB 36809, AG Nürnberg)

Re: [PATCH] drm/todo: Drop todo item to request memory regions in all fbdev drivers

[Helge Deller]

On 4/24/26 08:57, Thomas Zimmermann wrote:
> Hi
> 
> Am 23.04.26 um 22:55 schrieb Helge Deller:
>> This item is tagged for beginners, so often people not familiar with
>> the fbdev drivers think this is an easy task, start up their AI tools
>> and blindly send in the generated code as patches.
>>
>> The problem:
>> - Those patches often introduce bugs, so
>> - ideally want the code tested, since ressource misconfigurations
>>    often lead to failing drivers
>> - The patches are often unnecessary, since in the old machines with the
>>    old graphic cards resource conflicts usually don't happen as only one
>>    graphic card can be used at a time anyway.
>> - and today most relevant drivers have necessary patches already
>>    implemented.
>>
>> So, let's get rid of this todo item and silence the steady stream of
>> stupid patches.
> 
> I see that AI patches can be problematic, but reserving these
> regions is still the correct thing to do. Removing the TODO item
> will not change that.

Sure.
  
> Some background on why this item exists: we currently use aperture
> helpers [1] to manage ownership of the framebuffer memory during
> boot up. This is necessary to switch from the system-framebuffer
> driver (i..e, simplefb, simpledrm, etc) to the hardware's native
> driver. But this is all ad-hoc because Linux' resource management
> doesn't do this for us. Before we can integrate any such
> functionality, we have to fix all drivers to reserve their resources
> correctly.
> 
> If we remove the TODO item, we'd likely still want to move forward
> with improving resource management. If that breaks unfixed fbdev
> drivers, users would then also send bug reports.

Ok for me.

Helge

> And the other point is (again) that if there are no means of testing a driver and no information whether a driver is actually in used by anyone, it's maybe time to remove the driver.
> 
> [1] https://elixir.bootlin.com/linux/v7.0.1/source/drivers/video/aperture.c#L17
> 
> Best regards
> Thomas
> 
> 
>>
>> Signed-off-by: Helge Deller <deller@gmx.de>
>> ---
>>   Documentation/gpu/todo.rst | 16 ----------------
>>   1 file changed, 16 deletions(-)
>>
>> diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst
>> index bc9f14c8a2ec..b4dd64a8cc06 100644
>> --- a/Documentation/gpu/todo.rst
>> +++ b/Documentation/gpu/todo.rst
>> @@ -448,22 +448,6 @@ Contact: Thomas Zimmermann <tzimmermann@suse.de>
>>   Level: Intermediate
>> -Request memory regions in all fbdev drivers
>> ---------------------------------------------
>> -
>> -Old/ancient fbdev drivers do not request their memory properly.
>> -Go through these drivers and add code to request the memory regions
>> -that the driver uses. This requires adding calls to request_mem_region(),
>> -pci_request_region() or similar functions. Use helpers for managed cleanup
>> -where possible. Problematic areas include hardware that has exclusive ranges
>> -like VGA. VGA16fb does not request the range as it is expected.
>> -Drivers are pretty bad at doing this and there used to be conflicts among
>> -DRM and fbdev drivers. Still, it's the correct thing to do.
>> -
>> -Contact: Thomas Zimmermann <tzimmermann@suse.de>
>> -
>> -Level: Starter
>> -
>>   Remove driver dependencies on FB_DEVICE
>>   ---------------------------------------
>