From: "Sun, Daisy" <daisy.sun@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>,
Damien Lespiau <damien.lespiau@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/bdw: Broaden FBC resolution limit to 4096x4096
Date: Mon, 16 Jun 2014 13:41:36 -0700 [thread overview]
Message-ID: <539F5680.2000001@intel.com> (raw)
In-Reply-To: <20140616181549.GJ5821@phenom.ffwll.local>
Yes, the change starts from HSW. I'll update the patch.
what's the "rant" I need to insert? I was not in the list a year ago:),
having some trouble find the email as reference.
Any archives I can look into?
On 6/16/2014 11:15 AM, Daniel Vetter wrote:
> On Mon, Jun 16, 2014 at 06:11:45PM +0100, Damien Lespiau wrote:
>> On Mon, Jun 16, 2014 at 05:52:12PM +0100, Damien Lespiau wrote:
>>> From: Daisy Sun <daisy.sun@intel.com>
>>>
>>> Staring from BDW, the resolution limit of FBC has increased to
>>> 4096x4096>
>>>
>>> Issue: APDEV-2935
>>> Otc-Tracker: VIZ-3826
>>> Change-Id: I842f64e3cf2c0d18d29ef1bcfef3b9bb1f1764ac
>>> Signed-off-by: Daisy Sun <daisy.sun@intel.com>
>> Reviewed-by: Damien Lespiau <damien.lespiau@intel.com>
> Iirc 4kx4k is allowed on hsw already, albeit with the lower 2k lines being
> uncompressed. Please double-check bspec and update the patch.
>
> Also: Please insert rant here that I've written a mail a year ago about
> the piles of little issues in our fbc feature checking.
> -Daniel
>
>> --
>> Damien
>>
>>> ---
>>> drivers/gpu/drm/i915/intel_pm.c | 5 ++++-
>>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
>>> index 0b088fe..8cc60fc 100644
>>> --- a/drivers/gpu/drm/i915/intel_pm.c
>>> +++ b/drivers/gpu/drm/i915/intel_pm.c
>>> @@ -529,7 +529,10 @@ void intel_update_fbc(struct drm_device *dev)
>>> goto out_disable;
>>> }
>>>
>>> - if (IS_G4X(dev) || INTEL_INFO(dev)->gen >= 5) {
>>> + if (INTEL_INFO(dev)->gen >= 8) {
>>> + max_width = 4096;
>>> + max_height = 4096;
>>> + } else if (IS_G4X(dev) || INTEL_INFO(dev)->gen >= 5) {
>>> max_width = 4096;
>>> max_height = 2048;
>>> } else {
>>> --
>>> 1.8.3.1
>>>
>>> _______________________________________________
>>> Intel-gfx mailing list
>>> Intel-gfx@lists.freedesktop.org
>>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-06-16 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-16 16:52 [PATCH] drm/i915/bdw: Broaden FBC resolution limit to 4096x4096 Damien Lespiau
2014-06-16 17:11 ` Damien Lespiau
2014-06-16 18:15 ` Daniel Vetter
2014-06-16 20:41 ` Sun, Daisy [this message]
2014-06-16 21:49 ` Daniel Vetter
2014-06-16 22:55 ` Sun, Daisy
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=539F5680.2000001@intel.com \
--to=daisy.sun@intel.com \
--cc=damien.lespiau@intel.com \
--cc=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.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 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.