All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Widawsky <ben@bwidawsk.net>
To: SD <sd.domrep@yahoo.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: frame buffer compression and 915GM
Date: Sat, 28 May 2011 15:47:05 -0700	[thread overview]
Message-ID: <20110528224705.GA4342@lundgren.kumite> (raw)
In-Reply-To: <509117.6729.qm@web110507.mail.gq1.yahoo.com>

On Sat, May 28, 2011 at 01:50:12AM -0700, SD wrote:
> 
> 
> --- On Fri, 5/27/11, Ben Widawsky <ben@bwidawsk.net> wrote:
> 
> > From: Ben Widawsky <ben@bwidawsk.net>
> > Subject: Re: [Intel-gfx] frame buffer compression and 915GM
> > To: "SD" <sd.domrep@yahoo.com>
> > Cc: intel-gfx@lists.freedesktop.org
> > Date: Friday, May 27, 2011, 11:48 PM
> > On Fri, May 27, 2011 at 01:51:53AM
> > -0700, SD wrote:
> > > OK, thank you. I checked it, and I got unexpected
> > answer -
> > > 
> > > FBC unsupported on this chipset.
> > 
> > I'd need to know exactly which chipset you have. For
> > example. Ironlake
> > mobile, we disabled FBC because it was actually consuming
> > more power.
> > 
> > You can check your specific chipset, and look at the
> > has_fbc field here:
> > drivers/gpu/drm/i915/i915_drv.c
> > 
> > Ben
> > 
> 
> Thanks.
> I checked it out.
> You threw FBC from i915_drv since 2.6.33, because in 2.6.32 there was not any sign of pci_id detection. And since then I got awful screen picture quality, because I start to test with Fedora 12 and then jumped to Fedora 13 with 33 kernel, and since then never had normal picture - always flickers.
> 
> I know you are all very clever here and are thinking about some Watts, but I am, like a user, thinking about my eyes first and want to tell you that you did mistake.
> May be FBC uses more power (I am not sure about it, as long 3D performance on i915gm is "nothing" anyway), but it looks like FBC helps to produce nice and smooth picture on laptop LSD.

I don't think FBC should have any positive impact on the display, but I
suppose that is a subjective thing.

You should see Jesse's commit in keithp's drm-intel-next
(c1a9f047638b27e481d097910604316b8a0d132b). If you're capable of writing
code, I'd suggest you do the same thing for intel_i915gm_info where fbc
can be enabled, but is off by default. If not, hopefully I, or someone
else will get around to it eventually.

Ben

  reply	other threads:[~2011-05-28 22:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-26 19:29 frame buffer compression and 915GM SD
2011-05-27  1:53 ` Ben Widawsky
2011-05-27  8:51 ` SD
2011-05-27 14:50   ` Clemens Eisserer
2011-05-27 15:21     ` SD
2011-05-27 19:48   ` Ben Widawsky
2011-05-28  8:50     ` SD
2011-05-28 22:47       ` Ben Widawsky [this message]
2011-05-29  8:19         ` SD

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=20110528224705.GA4342@lundgren.kumite \
    --to=ben@bwidawsk.net \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sd.domrep@yahoo.com \
    /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.