Linux Framebuffer Layer development
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: "René Rebe" <rene@exactco.de>, linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] fbdev/tcx.c fix mem_map to correct smem_start offset
Date: Tue, 2 Dec 2025 19:43:34 +0100	[thread overview]
Message-ID: <dade2cdb-be65-4a69-a24c-ef99fd37306b@gmx.de> (raw)
In-Reply-To: <20251120.142400.712755331607709755.rene@exactco.de>

On 11/20/25 14:24, René Rebe wrote:
> 403ae52ac047 ("sparc: fix drivers/video/tcx.c warning") changed the
> physbase initializing breaking the user-space mmap, e.g. for Xorg
> entirely.
> 
> Fix fbdev mmap table so the sbus mmap helper work correctly, and
> not try to map vastly (physbase) offset memory.
> 
> Fixes: 403ae52ac047 ("sparc: fix drivers/video/tcx.c warning")
> Signed-off-by: René Rebe <rene@exactco.de>

Applied to fbdev.

Rene, shouldn't it be backported to all old Linux kernels?
Should I add a stable tag ?

Helge

  ---
>   drivers/video/fbdev/tcx.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/video/fbdev/tcx.c b/drivers/video/fbdev/tcx.c
> index f9a0085ad72b..ca9e84e8d860 100644
> --- a/drivers/video/fbdev/tcx.c
> +++ b/drivers/video/fbdev/tcx.c
> @@ -428,7 +428,7 @@ static int tcx_probe(struct platform_device *op)
>   			j = i;
>   			break;
>   		}
> -		par->mmap_map[i].poff = op->resource[j].start;
> +		par->mmap_map[i].poff = op->resource[j].start - info->fix.smem_start;
>   	}
>   
>   	info->fbops = &tcx_ops;


  reply	other threads:[~2025-12-02 18:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-20 13:24 [PATCH] fbdev/tcx.c fix mem_map to correct smem_start offset René Rebe
2025-12-02 18:43 ` Helge Deller [this message]
2025-12-02 18:50   ` René Rebe

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=dade2cdb-be65-4a69-a24c-ef99fd37306b@gmx.de \
    --to=deller@gmx.de \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=rene@exactco.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