From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Stefan Agner <stefan@agner.ch>
Cc: daniel.vetter@intel.com, dri-devel@lists.freedesktop.org
Subject: Re: [RFC] drm/fb-helper: reject any changes to the fbdev
Date: Wed, 12 Oct 2016 13:42:53 +0300 [thread overview]
Message-ID: <20161012104253.GT4329@intel.com> (raw)
In-Reply-To: <20161011231504.17688-1-stefan@agner.ch>
On Tue, Oct 11, 2016 at 04:15:04PM -0700, Stefan Agner wrote:
> The current fbdev emulation does not allow to push back changes in
> width, height or depth to KMS, hence reject any changes with an
> error. This makes sure that fbdev ioctl's fail properly and user
> space does not assume that changes succeeded.
>
> Signed-off-by: Stefan Agner <stefan@agner.ch>
> ---
> This rejects reconfiguration of framebuffer like
> fbset -rgba 5,6,5 -depth 16 (when in 24 bit mode by default)
> fbset -xres 123
>
> I think all users of drm_fb_helper_check_var use also the generic
> drm_fb_helper_set_par (or do otherwise not support changing size/
> depth). Hence, afaict, the change should be the right thing to do
> for all driver...
>
> drivers/gpu/drm/drm_fb_helper.c | 13 ++++++++-----
> 1 file changed, 8 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_fb_helper.c b/drivers/gpu/drm/drm_fb_helper.c
> index 03414bd..596c056 100644
> --- a/drivers/gpu/drm/drm_fb_helper.c
> +++ b/drivers/gpu/drm/drm_fb_helper.c
> @@ -1211,11 +1211,14 @@ int drm_fb_helper_check_var(struct fb_var_screeninfo *var,
> if (var->pixclock != 0 || in_dbg_master())
> return -EINVAL;
>
> - /* Need to resize the fb object !!! */
> - if (var->bits_per_pixel > fb->bits_per_pixel ||
> - var->xres > fb->width || var->yres > fb->height ||
> - var->xres_virtual > fb->width || var->yres_virtual > fb->height) {
> - DRM_DEBUG("fb userspace requested width/height/bpp is greater than current fb "
> + /*
> + * Changes struct fb_var_screeninfo are currently not pushed back
> + * to KMS, hence fail if different settings are requested.
> + */
> + if (var->bits_per_pixel != fb->bits_per_pixel ||
> + var->xres != fb->width || var->yres != fb->height ||
> + var->xres_virtual != fb->width || var->yres_virtual != fb->height) {
This still looks somewhat incomplete. Sounds like we should just
reject changes to everything except xoffset/yoffset.
> + DRM_DEBUG("fb userspace requested width/height/bpp different than current fb "
> "request %dx%d-%d (virtual %dx%d) > %dx%d-%d\n",
> var->xres, var->yres, var->bits_per_pixel,
> var->xres_virtual, var->yres_virtual,
> --
> 2.10.0
>
> _______________________________________________
> dri-devel mailing list
> dri-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/dri-devel
--
Ville Syrjälä
Intel OTC
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-10-12 10:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-11 23:15 [RFC] drm/fb-helper: reject any changes to the fbdev Stefan Agner
2016-10-12 7:01 ` Daniel Vetter
2016-10-12 9:37 ` Tomi Valkeinen
2016-10-17 14:43 ` Daniel Vetter
2016-10-12 10:42 ` Ville Syrjälä [this message]
2016-10-12 15:55 ` Stefan Agner
2016-10-12 16:12 ` Ville Syrjälä
2016-10-12 17:05 ` Stefan Agner
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=20161012104253.GT4329@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=stefan@agner.ch \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.