From: Robert Foss <robert.foss@collabora.com>
To: Chih-Wei Huang <cwhuang@android-x86.org>
Cc: Zach Reizner <zachr@chromium.org>,
Daniel Stone <daniels@collabora.com>,
Tomeu Vizoso <tomeu.vizoso@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: Fri, 22 Sep 2017 17:43:38 +0200 [thread overview]
Message-ID: <1506095018.2286.5.camel@collabora.com> (raw)
In-Reply-To: <CAKc24n30fmgu_TTRRhMSaEsh7u3239hHb1=TDjuCbdNOQWnaTA@mail.gmail.com>
Hey Chih-Wei,
On Fri, 2017-09-22 at 10:40 +0800, Chih-Wei Huang wrote:
> Great news!
> Thanks a lot to make it happen.
>
> I hope I am wrong.
> From my understanding most x86 GPUs still
> cannot work with drm_hwcomposer since
> they lack of atomic mode-setting API support
> required by drm_hwcomposer.
> Hope this could be addressed soon since
> drm_hwcomposer becomes a standard project of fd.o.
I haven't personally run drm_hwc ontop of any x86 hardware, but there
are people who do it.
The android-ia project has supported using drm_hwcomposer and an
alternative hwcomposer, so it would think there should be no issues.
>
> 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.
Rob.
_______________________________________________
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-22 15:43 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 [this message]
2017-09-25 2:44 ` Chih-Wei Huang
2017-09-25 3:25 ` Kondapally, Kalyan
2017-09-25 7:06 ` Tomeu Vizoso
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=1506095018.2286.5.camel@collabora.com \
--to=robert.foss@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=tomeu.vizoso@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 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.