The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Adam Jackson <ajax@redhat.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>,
	dri-devel@lists.freedesktop.org, David Airlie <airlied@linux.ie>,
	Dave Airlie <airlied@redhat.com>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:DRM DRIVER FOR QEMU'S CIRRUS DEVICE" 
	<virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH] drm/cirrus: flip default to 32bpp
Date: Mon, 9 Jul 2018 09:39:24 +0200	[thread overview]
Message-ID: <20180709073924.GB3008@phenom.ffwll.local> (raw)
In-Reply-To: <e127596f255261d78fdfe6f534a1000f60c3c605.camel@redhat.com>

On Fri, Jul 06, 2018 at 02:35:07PM -0400, Adam Jackson wrote:
> On Fri, 2018-07-06 at 11:12 +0200, Gerd Hoffmann wrote:
> > cirrus can handle 1024x768 (and slightly higher) with 24bpp depth.
> > cirrus can handle up to 800x600 with 32bpp.
> 
> 16bpp is maybe a better choice? Nobody's using cirrus because they care
> about color fidelity and it'll use less CPU to update. There's
> precedent here, mgag200 defaults to 16bpp on sufficiently memory-
> impaired devices.

Yeah nouveau does the same fallback to 16bpp if there's not enough vram.
So do a bunch of other drivers.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

  reply	other threads:[~2018-07-09  7:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-06  9:12 [PATCH] drm/cirrus: flip default to 32bpp Gerd Hoffmann
2018-07-06 18:35 ` Adam Jackson
2018-07-09  7:39   ` Daniel Vetter [this message]
2018-08-08  8:46     ` Gerd Hoffmann

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=20180709073924.GB3008@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@linux.ie \
    --cc=airlied@redhat.com \
    --cc=ajax@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kraxel@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox