From: John Stultz <john.stultz@linaro.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: "David Lechner" <david@lechnology.com>,
"Xinliang Liu" <xinliang.liu@linaro.org>,
"Intel Graphics Development" <intel-gfx@lists.freedesktop.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
"Noralf Trønnes" <noralf@tronnes.org>
Subject: Re: [PATCH v5 4/8] drm/cma-helper: Use the generic fbdev emulation
Date: Thu, 23 Aug 2018 14:12:46 -0700 [thread overview]
Message-ID: <CALAqxLVR8=ddbKhw-X-yoHpKEzLFTbckzTWdHz_FuTAg7Wr_iQ@mail.gmail.com> (raw)
In-Reply-To: <2601561.YhrFMFhLQ8@avalon>
On Thu, Aug 23, 2018 at 1:49 PM, Laurent Pinchart
<laurent.pinchart@ideasonboard.com> wrote:
> On Thursday, 23 August 2018 20:48:40 EEST John Stultz wrote:
>> On Thu, Aug 23, 2018 at 1:09 AM, Daniel Vetter <daniel@ffwll.ch> wrote:
>> > On Thu, Aug 23, 2018 at 10:46:15AM +0300, Laurent Pinchart wrote:
>> >> Possibly slightly out of topic, but we're in 2018, is there any plan to
>> >> make SurfaceFlinger move away from FBDEV ?
>> >
>> > Is surfaceflinger really using direct fbdev still (maybe for boot-up)? Or
>> > is this just an artifact of the mali blob hwcomposer backend?
>>
>> Mostly its due to the simple fbdev being a legacy solution on android
>> that works out of the box.
>> I do suspect the android devs hope to retire it, which is why I'm
>> working on getting things going w/ the drm_hwcomposer right now so we
>> can get away from the fbdev.
>
> That would be good news. Are there many Android components other than vendor-
> specific hwcomposer implementations that still use fbdev ?
So yea, I can't really speak about what the various vendors are doing,
as I don't really know, but I'm aware there are still a few (in some
cases major) vendors who still use fbdev on their shipping devices
with their custom hwcomposer code.
Other then that, to my knowledge AOSP only has a default fallback
hwcomposer that uses fbdev, which is what we've used here as we didn't
want to take the vendor's proprietary hwcomposer blob. But again,
moving to the drm_hwcomposer is the shiny bright future, as soon as a
few remaining issues are sorted upstream.
thanks
-john
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-08-23 21:12 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 16:03 [PATCH v5 0/8] drm: Add generic fbdev emulation Noralf Trønnes
2018-07-03 16:03 ` [PATCH v5 1/8] drm: Begin an API for in-kernel clients Noralf Trønnes
2018-07-03 16:03 ` [PATCH v5 2/8] drm/fb-helper: Add generic fbdev emulation .fb_probe function Noralf Trønnes
2018-07-03 16:03 ` [PATCH v5 3/8] drm/pl111: Set .gem_prime_vmap and .gem_prime_mmap Noralf Trønnes
2018-07-03 16:03 ` [PATCH v5 4/8] drm/cma-helper: Use the generic fbdev emulation Noralf Trønnes
2018-08-21 6:44 ` John Stultz
2018-08-21 8:44 ` Daniel Vetter
2018-08-21 14:59 ` Noralf Trønnes
2018-08-21 15:41 ` Daniel Vetter
2018-08-21 16:03 ` Noralf Trønnes
2018-08-21 16:46 ` Daniel Vetter
2018-08-21 18:43 ` John Stultz
2018-08-22 7:56 ` Daniel Vetter
2018-08-21 14:15 ` Noralf Trønnes
2018-08-23 4:14 ` John Stultz
2018-08-23 5:51 ` Daniel Vetter
2018-08-23 6:21 ` John Stultz
2018-08-23 7:37 ` Daniel Vetter
2018-08-23 16:49 ` Noralf Trønnes
2018-08-23 17:15 ` Daniel Vetter
2018-08-23 7:46 ` Laurent Pinchart
2018-08-23 8:09 ` Daniel Vetter
2018-08-23 17:48 ` John Stultz
2018-08-23 20:49 ` Laurent Pinchart
2018-08-23 21:12 ` John Stultz [this message]
2018-08-24 8:57 ` Laurent Pinchart
2018-08-23 17:38 ` John Stultz
2018-08-23 17:24 ` Ville Syrjälä
2018-08-23 17:42 ` John Stultz
2018-07-03 16:03 ` [PATCH v5 5/8] drm/debugfs: Add internal client debugfs file Noralf Trønnes
2018-07-03 16:03 ` [PATCH v5 6/8] drm/fb-helper: Finish the generic fbdev emulation Noralf Trønnes
2018-07-03 16:03 ` [PATCH v5 7/8] drm/tinydrm: Use drm_fbdev_generic_setup() Noralf Trønnes
2018-07-03 16:03 ` [PATCH v5 8/8] drm/cma-helper: Remove drm_fb_cma_fbdev_init_with_funcs() Noralf Trønnes
2018-07-03 16:15 ` ✗ Fi.CI.CHECKPATCH: warning for drm: Add generic fbdev emulation Patchwork
2018-07-03 16:18 ` ✗ Fi.CI.SPARSE: " Patchwork
2018-07-03 16:32 ` ✓ Fi.CI.BAT: success " Patchwork
2018-07-04 2:38 ` ✓ Fi.CI.IGT: " Patchwork
2018-07-04 8:19 ` [PATCH v5 0/8] " Daniel Vetter
2018-07-10 13:10 ` Noralf Trønnes
2018-08-23 6:25 ` ✗ Fi.CI.BAT: failure for drm: Add generic fbdev emulation (rev2) Patchwork
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='CALAqxLVR8=ddbKhw-X-yoHpKEzLFTbckzTWdHz_FuTAg7Wr_iQ@mail.gmail.com' \
--to=john.stultz@linaro.org \
--cc=david@lechnology.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=noralf@tronnes.org \
--cc=xinliang.liu@linaro.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;
as well as URLs for NNTP newsgroup(s).