From: Tomeu Vizoso <tomeu.vizoso@collabora.com>
To: Chih-Wei Huang <cwhuang@android-x86.org>,
Robert Foss <robert.foss@collabora.com>
Cc: Zach Reizner <zachr@chromium.org>,
Daniel Stone <daniels@collabora.com>,
Liviu Dudau <Liviu.Dudau@arm.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
Marissa Wall <marissaw@google.com>,
Kaveh Nasri <kaveh.nasri@intel.com>,
Kalyan Kondapally <kalyan.kondapally@intel.com>,
Stephane Marchesin <marcheu@chromium.org>
Subject: Re: drm_hwcomposer moving to fd.o
Date: Mon, 25 Sep 2017 09:06:55 +0200 [thread overview]
Message-ID: <37ef26c1-e0e1-bf0f-9608-550cb9c35b79@collabora.com> (raw)
In-Reply-To: <CAKc24n2Lr8sTreSwcaqHSXm3_RvWOs2WwmtNQ+QZxgEfkK_mvw@mail.gmail.com>
On 09/25/2017 04:44 AM, Chih-Wei Huang wrote:
> Hey Robert, thank you for the reply.
>
> 2017-09-22 23:43 GMT+08:00 Robert Foss <robert.foss@collabora.com>:
>> Hey Chih-Wei,
>> On Fri, 2017-09-22 at 10:40 +0800, Chih-Wei Huang wrote:
>
>> The android-ia project has supported using drm_hwcomposer and an
>> alternative hwcomposer, so it would think there should be no issues.
>
> By x86 GPUs, I meant i915(i965)/nouveau/radeon/amdgpu/virgl/vmwgfx.
> Among these only virgl works with the current drm_hwcomposer.
> All the others don't have a ready atomic mode-setting API to use it.
> That's the problem which should be addressed I meant.
Most if not all of those drivers support the atomic updates API in
mainline (and have for a few releases by now).
Regards,
Tomeu
> The android-ia doesn't support using fdo's drm_hwcomposer I think.
> They use an alternative hwcomposer [1] as you said.
> It looks very different than drm_hwcomposer though
> both rely on the similar (or same?) atomic API.
> Android-ia's kernel has also been patched to work with it.
> The vanilla kernel (at least LTS 4.9) can't work with [1]
> or drm_hwcomposer.
> Actually [1] only works with i915(i965) but we want
> a more generic hwcomposer like drm_hwcomposer.
>
> Please correct me if I am wrong.
>
>
> [1]: git://github.com/01org/IA-Hardware-Composer
>
>>> How about the gralloc?
>>> There are also several implementations
>>> scattered somewhere.
>>> I think it's also important to standardize it to fd.o
>>> and make it work with fd.o's drm_hwcomposer.
>>
>> Gralloc is a different story, and the right person to ask about it is
>> not me, but maybe Rob Herring.
>
>
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-09-25 7:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 23:52 drm_hwcomposer moving to fd.o Robert Foss
2017-09-22 2:40 ` Chih-Wei Huang
2017-09-22 15:43 ` Robert Foss
2017-09-25 2:44 ` Chih-Wei Huang
2017-09-25 3:25 ` Kondapally, Kalyan
2017-09-25 7:06 ` Tomeu Vizoso [this message]
2017-09-26 5:26 ` Daniel Vetter
2017-09-28 6:49 ` Chih-Wei Huang
2017-09-28 7:08 ` Daniel Vetter
2017-09-28 7:35 ` Tomeu Vizoso
2017-09-28 7:43 ` Tapani Pälli
2017-09-28 7:59 ` Daniel Vetter
2017-09-29 5:31 ` Chih-Wei Huang
2017-09-22 11:21 ` Jani Nikula
2017-09-22 15:23 ` Robert Foss
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=37ef26c1-e0e1-bf0f-9608-550cb9c35b79@collabora.com \
--to=tomeu.vizoso@collabora.com \
--cc=Liviu.Dudau@arm.com \
--cc=cwhuang@android-x86.org \
--cc=daniels@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kalyan.kondapally@intel.com \
--cc=kaveh.nasri@intel.com \
--cc=marcheu@chromium.org \
--cc=marissaw@google.com \
--cc=robert.foss@collabora.com \
--cc=zachr@chromium.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