Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Thomas Zimmermann <tzimmermann@suse.de>,
	Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/todo: Drop todo item to request memory regions in all fbdev drivers
Date: Fri, 24 Apr 2026 10:36:58 +0200	[thread overview]
Message-ID: <c5e49d34-f9b7-4d9e-a8ff-c2de3a3025fb@gmx.de> (raw)
In-Reply-To: <39ecf9f1-fd8d-4946-bb09-1041150d99eb@suse.de>

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

  reply	other threads:[~2026-04-24  8:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23 20:55 [PATCH] drm/todo: Drop todo item to request memory regions in all fbdev drivers Helge Deller
2026-04-24  6:43 ` Geert Uytterhoeven
2026-04-24  7:01   ` Thomas Zimmermann
2026-04-24  8:36     ` Helge Deller [this message]
2026-04-24  8:52       ` Thomas Zimmermann
2026-04-24  6:57 ` Thomas Zimmermann
2026-04-24  8:39   ` Helge Deller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c5e49d34-f9b7-4d9e-a8ff-c2de3a3025fb@gmx.de \
    --to=deller@gmx.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=tzimmermann@suse.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox