From: Maxime Ripard <maxime@cerno.tech>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: Javier Martinez Canillas <javierm@redhat.com>,
dri-devel@lists.freedesktop.org,
virtualization@lists.linux-foundation.org,
linux-graphics-maintainer@vmware.com, kraxel@redhat.com
Subject: Re: [PATCH 5/6] drm/fb-helper: Consolidate CONFIG_DRM_FBDEV_LEAK_PHYS_SMEM
Date: Fri, 17 Mar 2023 16:11:28 +0100 [thread overview]
Message-ID: <20230317151128.hwaaq4na7d7mifaw@houat> (raw)
In-Reply-To: <886052ee-69cd-8640-ea7f-c9e14f57651f@suse.de>
On Fri, Mar 17, 2023 at 01:51:42PM +0100, Thomas Zimmermann wrote:
> Hi
>
> Am 17.03.23 um 13:39 schrieb Javier Martinez Canillas:
> > Thomas Zimmermann <tzimmermann@suse.de> writes:
> >
> > > Consolidate all handling of CONFIG_DRM_FBDEV_LEAK_PHYS_SMEM by
> > > making the module parameter optional in drm_fb_helper.c.
> > >
> > > Without the config option, modules can set smem_start in struct
> > > fb_info for internal usage, but not export if to userspace. The
> > > address can only be exported by enabling the option and setting
> > > the module parameter. Also update the comment.
> > >
> >
> > I was going to ask at what point we could just get rid of this Kconfig
> > symbol since it already depends on EXPERT anyways so most distros will
> > not enable it.
> >
> > But I looked then and noticed that it was added just a few years ago in
> > commit 4be9bd10e22d "(drm/fb_helper: Allow leaking fbdev smem_start"),
> > so it seems that people still need that :(
>
> I don't even know which userspace drivers need this symbol. Probably
> something on Android.
At least the Mali (utgard) user-space stack uses it, including on
"regular" distributions.
I don't know about newest Mali generations.
Maxime
next prev parent reply other threads:[~2023-03-17 15:11 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 16:14 [PATCH 0/6] drm/fbdev-generic: Mandatory shadow buffering Thomas Zimmermann
2023-03-15 16:14 ` [PATCH 1/6] drm/fbdev-generic: Always use " Thomas Zimmermann
2023-03-17 11:47 ` Javier Martinez Canillas
2023-03-17 12:19 ` Thomas Zimmermann
2023-03-15 16:14 ` [PATCH 2/6] drm/fbdev-generic: Remove unused prefer_shadow_fbdev flag Thomas Zimmermann
2023-03-16 2:16 ` Zack Rusin
2023-03-16 9:38 ` Thomas Zimmermann
2023-03-17 12:04 ` Javier Martinez Canillas
2023-03-15 16:14 ` [PATCH 3/6] drm/fb-helper: Export drm_fb_helper_release_info() Thomas Zimmermann
2023-03-17 12:07 ` Javier Martinez Canillas
2023-03-15 16:14 ` [PATCH 4/6] drm/fbdev-generic: Clean up after failed probing Thomas Zimmermann
2023-03-17 12:24 ` Javier Martinez Canillas
2023-03-20 12:44 ` Thomas Zimmermann
2023-03-15 16:14 ` [PATCH 5/6] drm/fb-helper: Consolidate CONFIG_DRM_FBDEV_LEAK_PHYS_SMEM Thomas Zimmermann
2023-03-17 12:39 ` Javier Martinez Canillas
2023-03-17 12:51 ` Thomas Zimmermann
2023-03-17 15:11 ` Maxime Ripard [this message]
2023-03-17 16:08 ` Thomas Zimmermann
2023-03-17 16:27 ` Maxime Ripard
2023-03-15 16:14 ` [PATCH 6/6] drm/fbdev-generic: Rename symbols Thomas Zimmermann
2023-03-17 12:40 ` Javier Martinez Canillas
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=20230317151128.hwaaq4na7d7mifaw@houat \
--to=maxime@cerno.tech \
--cc=dri-devel@lists.freedesktop.org \
--cc=javierm@redhat.com \
--cc=kraxel@redhat.com \
--cc=linux-graphics-maintainer@vmware.com \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux-foundation.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;
as well as URLs for NNTP newsgroup(s).