All of lore.kernel.org
 help / color / mirror / Atom feed
From: hean.loong.ong@intel.com (Ong, Hean Loong)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH10 3/3] ARM:drm ivip Intel FPGA Video and Image Processing Suite
Date: Wed, 15 Aug 2018 01:44:46 +0000	[thread overview]
Message-ID: <1534297485.3035.2.camel@intel.com> (raw)
In-Reply-To: <4c9770ce-999f-2ec3-60fb-397c4cec23a2@kernel.org>

On Tue, 2018-08-14 at 10:46 -0500, Dinh Nguyen wrote:
> 
> 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.
> 
During Cyclone5 SoCkit it was the older version of the Frambuffer. From
the IP owner the FrameBuffer II design is only available for Arria10

> Dinh
> 

WARNING: multiple messages have this Message-ID (diff)
From: "Ong, Hean Loong" <hean.loong.ong@intel.com>
To: "dinguyen@kernel.org" <dinguyen@kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"airlied@linux.ie" <airlied@linux.ie>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Vandervennet, Yves" <yves.vandervennet@intel.com>,
	"See, Chin Liang" <chin.liang.see@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH10 3/3] ARM:drm ivip Intel FPGA Video and Image Processing Suite
Date: Wed, 15 Aug 2018 01:44:46 +0000	[thread overview]
Message-ID: <1534297485.3035.2.camel@intel.com> (raw)
In-Reply-To: <4c9770ce-999f-2ec3-60fb-397c4cec23a2@kernel.org>

On Tue, 2018-08-14 at 10:46 -0500, Dinh Nguyen wrote:
> 
> 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.
> 
During Cyclone5 SoCkit it was the older version of the Frambuffer. From
the IP owner the FrameBuffer II design is only available for Arria10

> Dinh
> 
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

WARNING: multiple messages have this Message-ID (diff)
From: "Ong, Hean Loong" <hean.loong.ong@intel.com>
To: "dinguyen@kernel.org" <dinguyen@kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"airlied@linux.ie" <airlied@linux.ie>
Cc: "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"See, Chin Liang" <chin.liang.see@intel.com>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"Vandervennet, Yves" <yves.vandervennet@intel.com>
Subject: Re: [PATCH10 3/3] ARM:drm ivip Intel FPGA Video and Image Processing Suite
Date: Wed, 15 Aug 2018 01:44:46 +0000	[thread overview]
Message-ID: <1534297485.3035.2.camel@intel.com> (raw)
In-Reply-To: <4c9770ce-999f-2ec3-60fb-397c4cec23a2@kernel.org>

On Tue, 2018-08-14 at 10:46 -0500, Dinh Nguyen wrote:
> 
> 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.
> 
During Cyclone5 SoCkit it was the older version of the Frambuffer. From
the IP owner the FrameBuffer II design is only available for Arria10

> Dinh
> 

  reply	other threads:[~2018-08-15  1:44 UTC|newest]

Thread overview: 27+ 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 ` 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 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  8:57   ` Hean-Loong, Ong
2018-08-14  8:57   ` Hean-Loong, Ong
2018-08-14 15:46   ` Dinh Nguyen
2018-08-14 15:46     ` Dinh Nguyen
2018-08-15  1:44     ` Ong, Hean Loong [this message]
2018-08-15  1:44       ` Ong, Hean Loong
2018-08-15  1:44       ` Ong, Hean Loong
2018-08-15 12:26   ` Noralf Trønnes
2018-08-15 12:26     ` Noralf Trønnes
2018-08-15 12:26     ` Noralf Trønnes
2018-08-16  8:33     ` Ong, Hean Loong
2018-08-16  8:33       ` Ong, Hean Loong
2018-08-16  8:33       ` Ong, Hean Loong
2018-08-16  9:10       ` Noralf Trønnes
2018-08-16  9:10         ` Noralf Trønnes
2018-08-14 15:48 ` [PATCH10 0/3] " Dinh Nguyen
2018-08-14 15:48   ` Dinh Nguyen
2018-08-14 15:48   ` Dinh Nguyen
2018-08-15  1:42   ` Ong, Hean Loong
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=1534297485.3035.2.camel@intel.com \
    --to=hean.loong.ong@intel.com \
    --cc=linux-arm-kernel@lists.infradead.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.