From: Pawel Moll <pawel.moll@arm.com>
To: Show Liu <show.liu@linaro.org>
Cc: "dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
"tom.gall@linaro.org" <tom.gall@linaro.org>,
"t.katayama@jp.fujitsu.com" <t.katayama@jp.fujitsu.com>,
"vikas.sajjan@linaro.org" <vikas.sajjan@linaro.org>,
"linaro-kernel@lists.linaro.org" <linaro-kernel@lists.linaro.org>
Subject: Re: [PATCH 0/2][RFC] CDFv2 for VExpress HDLCD DVI output support
Date: Wed, 17 Jul 2013 11:49:49 +0100 [thread overview]
Message-ID: <1374058189.3146.107.camel@hornet> (raw)
In-Reply-To: <1374055737-6643-1-git-send-email-show.liu@linaro.org>
On Wed, 2013-07-17 at 11:08 +0100, Show Liu wrote:
> This series patches extend Pawel's patches to
> Versatile Express HDLCD DVI output support.
> Before apply this patches, please apply Pawel's patches first.
> This series patches implements base on Linaro release 13.06 branch "ll_20130621.0".
>
> here is Pawel's patches
> [1] http://lists.freedesktop.org/archives/dri-devel/2013-April/037519.html
Glad to see someone thinking the same way ;-) Thanks for trying it and
particularly for the fixes in vexpress-* code. I'll keep them in mind
when the time comes :-)
Of course neither the CDF patch nor the HDLCD driver are upstream yet.
Laurent promised to post next (hopefully final ;-) version of his
patches soon, but the API has apparently changed so we'll have to adapt
to it. As to the HDLCD driver - there is some work going on converting
it to DRM/KMS and upstreaming as such, using CDF if it's available by
that time as well.
Paweł
next prev parent reply other threads:[~2013-07-17 10:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-17 10:08 [PATCH 0/2][RFC] CDFv2 for VExpress HDLCD DVI output support Show Liu
2013-07-17 10:08 ` [PATCH 1/2] Fixed for compatible with kernel 3.10.0-rc6 Show Liu
2013-07-17 10:08 ` [PATCH 2/2] CDFv2 for VExpress HDLCD DVI output support Show Liu
2013-07-17 10:49 ` Pawel Moll [this message]
2013-07-17 11:50 ` [PATCH 0/2][RFC] " Laurent Pinchart
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=1374058189.3146.107.camel@hornet \
--to=pawel.moll@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-media@vger.kernel.org \
--cc=show.liu@linaro.org \
--cc=t.katayama@jp.fujitsu.com \
--cc=tom.gall@linaro.org \
--cc=vikas.sajjan@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 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.