From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: "Ong, Hean Loong" <hean.loong.ong@intel.com>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-fbdev@vger.kernel.org>
Subject: Re: [PATCHv0 1/1] fbdev: add Intel FPGA FRAME BUFFER driver
Date: Wed, 23 Nov 2016 09:30:09 +0200 [thread overview]
Message-ID: <b38e19f1-0be9-37ea-94cd-d37d8b8aa7f3@ti.com> (raw)
In-Reply-To: <1479287278-5192-1-git-send-email-hean.loong.ong@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1084 bytes --]
Hi,
On 16/11/16 11:07, Ong, Hean Loong wrote:
> From: Ong Hean Loong <hean.loong.ong@intel.com>
>
> This patch enables the display port IP driver for
> Intel Arria 10 SOCFPGA Golden Hardware
> Reference Design (GHRD).
>
> The driver requires enabling the options such as
> Coheherent Memory Allocation,
> Intel FPGA Frame Buffer, Frame Buffer Conasole
>
> Signed-off-by: Ong Hean Loong <hean.loong.ong@intel.com>
> ---
> .../devicetree/bindings/video/intelfpgavipfb.txt | 22 ++
> MAINTAINERS | 6 +
> drivers/video/fbdev/Kconfig | 15 +
> drivers/video/fbdev/Makefile | 1 +
> drivers/video/fbdev/intelfpgavipfb.c | 302 ++++++++++++++++++++
> 5 files changed, 346 insertions(+), 0 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/video/intelfpgavipfb.txt
> create mode 100644 drivers/video/fbdev/intelfpgavipfb.c
As mentioned by Rob and Alan, no new fbdev drivers please. Write a DRM
driver for this.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-11-23 7:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 9:07 Ong, Hean Loong
2016-11-16 12:45 ` kbuild test robot
2016-11-16 13:33 ` kbuild test robot
2016-11-18 14:09 ` Rob Herring
2016-11-18 14:15 ` One Thousand Gnomes
2016-11-18 18:56 ` Rob Herring
2016-11-21 2:41 ` Ong, Hean Loong
2016-11-23 7:30 ` Tomi Valkeinen [this message]
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=b38e19f1-0be9-37ea-94cd-d37d8b8aa7f3@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hean.loong.ong@intel.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®