From: Helge Deller <deller@gmx.de>
To: Javier Garcia <rampxxxx@gmail.com>
Cc: linux-fbdev@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, shuah@kernel.org
Subject: Re: [PATCH] fbdev: vga16fb: Request memory region.
Date: Mon, 27 Oct 2025 21:07:21 +0100 [thread overview]
Message-ID: <6c565f4c-ef05-45f2-9a82-cbba4a11cc07@gmx.de> (raw)
In-Reply-To: <CABPJ0vgtpjh2q605TifawiS36qAS+OO_dAnYVGsqd03GSXZp+g@mail.gmail.com>
On 10/27/25 19:02, Javier Garcia wrote:
> Hi,
>
> Helge Deller, any comment on this patch?
Well, it doesn't hurt, as it will not abort (as before) even if the region is occupied.
In that sense, I don't see a problem to add it.
But you are missing to release the memory when the driver is released
via vga16fb_remove.
If you send an updated/fixed patch I will apply it to the fbdev tree
to get some testing.
Helge
> ---
> Javier Garcia
>
>
> On Thu, 16 Oct 2025 at 19:18, Javier Garcia <rampxxxx@gmail.com> wrote:
>>
>> This patch reserve and release VGA memory region with `*_mem_region`
>> fn's.
>>
>> This align with Documentation/drm/todo.rst
>> "Request memory regions in all fbdev drivers"
>>
>> I've tested with kernel and qemu both 32bits.
>>
>> Signed-off-by: Javier Garcia <rampxxxx@gmail.com>
>> ---
>>
>> When I've run the code always return -EBUSY which makes sense as
>> mem is already requested,`/proc/iomem` shows `000a0000-000bffff : Video RAM area`.
>>
>> I've seen that `cirrusfb` has this kind of code wrapped up with `#if 0`, and I
>> wonder if it makes sense to also wrap up with `#if 0`, at least , in
>> that way the code gets commented about expected behavior.
>>
>>
>> drivers/video/fbdev/vga16fb.c | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/drivers/video/fbdev/vga16fb.c b/drivers/video/fbdev/vga16fb.c
>> index eedab14c7d51..f506bf144a97 100644
>> --- a/drivers/video/fbdev/vga16fb.c
>> +++ b/drivers/video/fbdev/vga16fb.c
>> @@ -1319,6 +1319,11 @@ static int vga16fb_probe(struct platform_device *dev)
>> if (ret)
>> return ret;
>>
>> + if (!request_mem_region(vga16fb_fix.smem_start, vga16fb_fix.smem_len,
>> + "vga16b")) {
>> + dev_err(&dev->dev,"vga16b: cannot reserve video memory at 0x%lx\n",
>> + vga16fb_fix.smem_start);
>> + }
>> printk(KERN_DEBUG "vga16fb: initializing\n");
>> info = framebuffer_alloc(sizeof(struct vga16fb_par), &dev->dev);
>>
>> @@ -1398,6 +1403,8 @@ static int vga16fb_probe(struct platform_device *dev)
>> err_ioremap:
>> framebuffer_release(info);
>> err_fb_alloc:
>> + release_mem_region(vga16fb_fix.smem_start,
>> + vga16fb_fix.smem_len);
>> return ret;
>> }
>>
>> --
>> 2.50.1
>>
next prev parent reply other threads:[~2025-10-27 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 17:18 Javier Garcia
2025-10-27 18:02 ` Javier Garcia
2025-10-27 20:07 ` Helge Deller [this message]
2025-10-28 19:16 ` [PATCH v2] " Javier Garcia
2025-10-28 21:09 ` Helge Deller
2025-11-08 9:33 ` [PATCH v3] " Javier Garcia
2025-11-15 7:31 ` Javier Garcia
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=6c565f4c-ef05-45f2-9a82-cbba4a11cc07@gmx.de \
--to=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rampxxxx@gmail.com \
--cc=shuah@kernel.org \
/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
all inboxes | Powered by JetHome®