From: Eric Anholt <eric@anholt.net>
To: Maxime Ripard <maxime.ripard@bootlin.com>
Cc: eben@raspberrypi.org, Maxime Ripard <maxime.ripard@bootlin.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
dri-devel@lists.freedesktop.org,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
Sean Paul <seanpaul@chromium.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] drm/vc4: Use 16bpp by default for the fbdev buffer
Date: Wed, 06 Mar 2019 09:32:01 -0800 [thread overview]
Message-ID: <87ef7jkiy6.fsf@anholt.net> (raw)
In-Reply-To: <20190306140245.21973-1-maxime.ripard@bootlin.com>
[-- Attachment #1.1: Type: text/plain, Size: 727 bytes --]
Maxime Ripard <maxime.ripard@bootlin.com> writes:
> The preferred bpp for the fbdev emulation buffer has been 32 so far, which
> means that by default we will allocate an 8MB buffer with a 1920x1080
> resolution.
>
> Worse this memory will be allocated from the CMA pool, and will never be
> freed even if we don't use the fbdev emulation. Therefore, reducing it is a
> big deal, and switching to 16bpp by default will gain us around 4MB at
> 1920x1080, while keeping decent color depth. And users still have the
> option to switch to 32bpp using the kernel command line.
Reviewed-by: Eric Anholt <eric@anholt.net>
This matches the defaults used by the bcm2708 fbdev driver that we're
trying to get people to switch off of.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Eric Anholt <eric@anholt.net>
Cc: eben@raspberrypi.org, Maxime Ripard <maxime.ripard@bootlin.com>,
dri-devel@lists.freedesktop.org,
Paul Kocialkowski <paul.kocialkowski@bootlin.com>,
Sean Paul <seanpaul@chromium.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] drm/vc4: Use 16bpp by default for the fbdev buffer
Date: Wed, 06 Mar 2019 09:32:01 -0800 [thread overview]
Message-ID: <87ef7jkiy6.fsf@anholt.net> (raw)
In-Reply-To: <20190306140245.21973-1-maxime.ripard@bootlin.com>
[-- Attachment #1.1: Type: text/plain, Size: 727 bytes --]
Maxime Ripard <maxime.ripard@bootlin.com> writes:
> The preferred bpp for the fbdev emulation buffer has been 32 so far, which
> means that by default we will allocate an 8MB buffer with a 1920x1080
> resolution.
>
> Worse this memory will be allocated from the CMA pool, and will never be
> freed even if we don't use the fbdev emulation. Therefore, reducing it is a
> big deal, and switching to 16bpp by default will gain us around 4MB at
> 1920x1080, while keeping decent color depth. And users still have the
> option to switch to 32bpp using the kernel command line.
Reviewed-by: Eric Anholt <eric@anholt.net>
This matches the defaults used by the bcm2708 fbdev driver that we're
trying to get people to switch off of.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-03-06 17:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 14:02 [PATCH] drm/vc4: Use 16bpp by default for the fbdev buffer Maxime Ripard
2019-03-06 14:02 ` Maxime Ripard
2019-03-06 15:06 ` Paul Kocialkowski
2019-03-06 15:06 ` Paul Kocialkowski
2019-03-06 17:32 ` Eric Anholt [this message]
2019-03-06 17:32 ` Eric Anholt
2019-03-07 12:14 ` Maxime Ripard
2019-03-07 12:14 ` Maxime Ripard
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=87ef7jkiy6.fsf@anholt.net \
--to=eric@anholt.net \
--cc=dri-devel@lists.freedesktop.org \
--cc=eben@raspberrypi.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=maxime.ripard@bootlin.com \
--cc=paul.kocialkowski@bootlin.com \
--cc=seanpaul@chromium.org \
--cc=thomas.petazzoni@bootlin.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.