All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Tobias Jakobi <tjakobi@math.uni-bielefeld.de>
Cc: daniel.vetter@intel.com, s.christ@phytec.de,
	ML dri-devel <dri-devel@lists.freedesktop.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH v2 1/2] drm/cma-helper: Add multi buffer support for cma fbdev
Date: Thu, 16 Feb 2017 19:41:35 +0100	[thread overview]
Message-ID: <20170216184135.r3a6dvaoyhxwdcr7@lukather> (raw)
In-Reply-To: <88d1fd86-b21b-c36e-8817-563bd660a0cf@math.uni-bielefeld.de>


[-- Attachment #1.1: Type: text/plain, Size: 1244 bytes --]

Hi,

On Thu, Feb 16, 2017 at 01:28:24PM +0100, Tobias Jakobi wrote:
> Hello,
> 
> I'm not sure if I'm missing something here, but I don't see how this is
> supposed to work.
> 
> This just multiplies the height of the drm_mode_fb_cmd2 object with the
> number of buffers. Let's say I have width=1024, height=768, then now I
> have a framebuffer which has height=2304 (in the num_buffers=3 case). At
> some point this FB is set as the primary plane, giving us a 1024x2304
> mode. I don't think that this is intended.
> 
> In my opinion this multi-buffer thing should touch drm_mode_fb_cmd2 at
> all. The underlying BO should be larger, but not the FB itself. If this
> is supposed to work, then the fbdev helpers should create as many FBs as
> there are buffers, and then offset each of these FB into the BO.

This only increases the virtual resolution, not the visible one.

> What I'm also not seeing is code that handles the fbdev's virtual
> resolutions. After all num_buffers should only increase those. Same for
> the panning ioctl().

This is already implemented through drm_fb_helper_pan_display.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2017-02-17  8:39 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16 12:28 [PATCH v2 1/2] drm/cma-helper: Add multi buffer support for cma fbdev Tobias Jakobi
2017-02-16 18:41 ` Maxime Ripard [this message]
2017-02-17 12:49   ` Tobias Jakobi
  -- strict thread matches above, loose matches on Subject: below --
2017-02-02 10:31 [PATCH v2 0/2] drm: Support framebuffer panning Maxime Ripard
2017-02-02 10:31 ` [PATCH v2 1/2] drm/cma-helper: Add multi buffer support for cma fbdev Maxime Ripard
2017-02-02 10:31   ` Maxime Ripard
2017-02-09 17:04   ` Daniel Vetter
2017-02-09 17:04     ` Daniel Vetter
2017-02-10 15:27     ` Maxime Ripard
2017-02-10 15:27       ` Maxime Ripard
2017-02-12 12:28   ` Laurent Pinchart
2017-02-12 12:28     ` Laurent Pinchart
2017-02-13 10:54     ` Maxime Ripard
2017-02-13 10:54       ` Maxime Ripard
2017-02-13 11:20       ` Daniel Stone
2017-02-13 11:20         ` Daniel Stone
2017-02-14 20:09         ` Daniel Vetter
2017-02-14 20:09           ` Daniel Vetter
2017-02-14 21:25           ` Laurent Pinchart
2017-02-14 21:25             ` Laurent Pinchart
2017-02-15 12:51             ` Maxime Ripard
2017-02-15 12:51               ` Maxime Ripard
2017-02-17 11:30               ` Laurent Pinchart
2017-02-15 12:38         ` Maxime Ripard
2017-02-15 12:38           ` Maxime Ripard
2017-02-17 11:23           ` Laurent Pinchart
2017-02-17 11:23             ` Laurent Pinchart

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=20170216184135.r3a6dvaoyhxwdcr7@lukather \
    --to=maxime.ripard@free-electrons.com \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=s.christ@phytec.de \
    --cc=tjakobi@math.uni-bielefeld.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 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.