From: Dinh Nguyen <dinguyen@kernel.org>
To: "Hean-Loong, Ong" <hean.loong.ong@intel.com>,
Rob Herring <robh+dt@kernel.org>, David Airlie <airlied@linux.ie>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org, yves.vandervennet@intel.com,
chin.liang.see@intel.com
Subject: Re: [PATCH10 3/3] ARM:drm ivip Intel FPGA Video and Image Processing Suite
Date: Tue, 14 Aug 2018 10:46:54 -0500 [thread overview]
Message-ID: <4c9770ce-999f-2ec3-60fb-397c4cec23a2@kernel.org> (raw)
In-Reply-To: <1534237029-2648-4-git-send-email-hean.loong.ong@intel.com>
On 08/14/2018 03:57 AM, Hean-Loong, Ong wrote:
> From: Ong Hean Loong <hean.loong.ong@intel.com>
>
> Driver for Intel FPGA Video and Image Processing Suite Frame Buffer II.
> The driver only supports the Intel Arria10 devkit and its variants.
Why only Arria10? That's not true is it? I remember running a version of
this on the Cyclone5 SoCKit.
Dinh
next prev parent reply other threads:[~2018-08-14 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 8:57 [PATCH10 0/3] Intel FPGA Video and Image Processing Suite Hean-Loong, Ong
2018-08-14 8:57 ` [PATCH10 1/3] ARM:dt-bindings:display " Hean-Loong, Ong
2018-08-14 14:43 ` Rob Herring
2018-08-14 8:57 ` [PATCH10 2/3] ARM:socfpga-defconfig " Hean-Loong, Ong
2018-08-14 8:57 ` [PATCH10 3/3] ARM:drm ivip " Hean-Loong, Ong
2018-08-14 15:46 ` Dinh Nguyen [this message]
2018-08-15 1:44 ` Ong, Hean Loong
2018-08-15 12:26 ` Noralf Trønnes
2018-08-16 8:33 ` Ong, Hean Loong
2018-08-16 9:10 ` Noralf Trønnes
2018-08-14 15:48 ` [PATCH10 0/3] " Dinh Nguyen
2018-08-15 1:42 ` Ong, Hean Loong
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=4c9770ce-999f-2ec3-60fb-397c4cec23a2@kernel.org \
--to=dinguyen@kernel.org \
--cc=airlied@linux.ie \
--cc=chin.liang.see@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hean.loong.ong@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=yves.vandervennet@intel.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 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).