From: Damien Lespiau Subject: Re: [PATCH 1/3] drm/i915: Don't set mode_config's cursor size Date: Tue, 25 Mar 2014 18:51:25 +0000 Message-ID: <20140325185125.GG1729@strange.amr.corp.intel.com> References: <1395758972-31316-1-git-send-email-damien.lespiau@intel.com> <1395758972-31316-2-git-send-email-damien.lespiau@intel.com> <20140325145456.GC1719@nuc-i3427.alporthouse.com> <20140325145918.GD8248@strange.amr.corp.intel.com> <20140325150916.GD1719@nuc-i3427.alporthouse.com> <20140325160529.GA1729@strange.amr.corp.intel.com> <20140325163824.GG1719@nuc-i3427.alporthouse.com> <20140325165704.GD1729@strange.amr.corp.intel.com> <20140325182326.GJ26878@phenom.ffwll.local> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <20140325182326.GJ26878@phenom.ffwll.local> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" To: Daniel Vetter Cc: intel-gfx@lists.freedesktop.org, Sagar Kamble , DRI Development List-Id: dri-devel@lists.freedesktop.org On Tue, Mar 25, 2014 at 07:23:26PM +0100, Daniel Vetter wrote: > Or we simply do this per-pixel format with one for each framebuffer plane, > i.e. > > struct drm_get_plane_fb_limits { > uint32_t plane_id; /* in */ > uint32_t fourcc; /* in */ > struct drm_plane_limits limits[MAX_FOURCC_PLANES]; > /* the stuff above for all possible planes of a fourcc code */ > } > > Saner drivers could then return the same thing for all fourccs codes in > their backend. Some of the limits are definitely per format. Plane max dimensions are a good example of a limit that can change per-format (8bpp Vs 10bpp to be contained within the same max bandwidth of the hw). -- Damien