diff for duplicates of <1534297365.3035.0.camel@intel.com> diff --git a/a/1.txt b/N1/1.txt index 6014d58..f1568ea 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -4,16 +4,16 @@ On Tue, 2018-08-14 at 10:48 -0500, Dinh Nguyen wrote: > > > > From: Ong, Hean Loong <hean.loong.ong@intel.com> > > -> > The FPGA FrameBuffer Soft IP could be seen??as the GPU and the DRM -> > driver patch? +> > The FPGA FrameBuffer Soft IP could be seen as the GPU and the DRM +> > driver patch > > here is allocating memory for information to be streamed from the -> > ARM/Linux? +> > ARM/Linux > > to the display port. Basically the driver just wraps the -> > information such as? +> > information such as > > the pixels to be drawn by the FPGA FrameBuffer 2. > > > > The piece of hardware in discussion is the SoC FPGA where Linux -> > runs on the? +> > runs on the > > ARM chip and the FGPA is driven by its NIOS soft core with its own > > proprietary firmware. > This driver doesn't have to ARM specific does it? @@ -21,42 +21,42 @@ On Tue, 2018-08-14 at 10:48 -0500, Dinh Nguyen wrote: > > > > > > For example the application from the ARM Linux would have to write -> > information? +> > information > > on the /dev/fb0 with the information stored in the SDRAM to be -> > fetched by the? +> > fetched by the > > FPGA framebuffer IP and displayed on the Display Port Monitor. > > > > > > Ong Hean Loong (2): -> > ? ARM:socfpga-defconfig Intel FPGA Video and Image Processing Suite -> > ? ARM:drm ivip Intel FPGA Video and Image Processing Suite +> > ARM:socfpga-defconfig Intel FPGA Video and Image Processing Suite +> > ARM:drm ivip Intel FPGA Video and Image Processing Suite > > > > Ong, Hean Loong (1): -> > ? ARM:dt-bindings:display Intel FPGA Video and Image Processing +> > ARM:dt-bindings:display Intel FPGA Video and Image Processing > > Suite > > -> > ?.../devicetree/bindings/display/altr,vip-fb2.txt???|???63 +++++++ -> > ?arch/arm/configs/socfpga_defconfig?????????????????|????5 + -> > ?drivers/gpu/drm/Kconfig????????????????????????????|????2 + -> > ?drivers/gpu/drm/Makefile???????????????????????????|????1 + -> > ?drivers/gpu/drm/ivip/Kconfig???????????????????????|???14 ++ -> > ?drivers/gpu/drm/ivip/Makefile??????????????????????|????9 + -> > ?drivers/gpu/drm/ivip/intel_vip_conn.c??????????????|???95 +> > .../devicetree/bindings/display/altr,vip-fb2.txt | 63 +++++++ +> > arch/arm/configs/socfpga_defconfig | 5 + +> > drivers/gpu/drm/Kconfig | 2 + +> > drivers/gpu/drm/Makefile | 1 + +> > drivers/gpu/drm/ivip/Kconfig | 14 ++ +> > drivers/gpu/drm/ivip/Makefile | 9 + +> > drivers/gpu/drm/ivip/intel_vip_conn.c | 95 > > ++++++++++ -> > ?drivers/gpu/drm/ivip/intel_vip_core.c??????????????|??161 +> > drivers/gpu/drm/ivip/intel_vip_core.c | 161 > > ++++++++++++++++ -> > ?drivers/gpu/drm/ivip/intel_vip_drv.h???????????????|???52 ++++++ -> > ?drivers/gpu/drm/ivip/intel_vip_of.c????????????????|??193 +> > drivers/gpu/drm/ivip/intel_vip_drv.h | 52 ++++++ +> > drivers/gpu/drm/ivip/intel_vip_of.c | 193 > > ++++++++++++++++++++ -> > ?10 files changed, 595 insertions(+), 0 deletions(-) -> > ?create mode 100644 +> > 10 files changed, 595 insertions(+), 0 deletions(-) +> > create mode 100644 > > Documentation/devicetree/bindings/display/altr,vip-fb2.txt -> > ?create mode 100644 drivers/gpu/drm/ivip/Kconfig -> > ?create mode 100644 drivers/gpu/drm/ivip/Makefile -> > ?create mode 100644 drivers/gpu/drm/ivip/intel_vip_conn.c -> > ?create mode 100644 drivers/gpu/drm/ivip/intel_vip_core.c -> > ?create mode 100644 drivers/gpu/drm/ivip/intel_vip_drv.h -> > ?create mode 100644 drivers/gpu/drm/ivip/intel_vip_of.c +> > create mode 100644 drivers/gpu/drm/ivip/Kconfig +> > create mode 100644 drivers/gpu/drm/ivip/Makefile +> > create mode 100644 drivers/gpu/drm/ivip/intel_vip_conn.c +> > create mode 100644 drivers/gpu/drm/ivip/intel_vip_core.c +> > create mode 100644 drivers/gpu/drm/ivip/intel_vip_drv.h +> > create mode 100644 drivers/gpu/drm/ivip/intel_vip_of.c > > > Can you clarify your commit header? What is "PATCH10", is it version > 10? diff --git a/a/content_digest b/N1/content_digest index 87c6625..3ec620e 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,9 +1,19 @@ "ref\01534237029-2648-1-git-send-email-hean.loong.ong@intel.com\0" "ref\03720ba74-947a-1b5d-5f5b-1ef03d5941aa@kernel.org\0" - "From\0hean.loong.ong@intel.com (Ong, Hean Loong)\0" - "Subject\0[PATCH10 0/3] Intel FPGA Video and Image Processing Suite\0" + "From\0Ong, Hean Loong <hean.loong.ong@intel.com>\0" + "Subject\0Re: [PATCH10 0/3] Intel FPGA Video and Image Processing Suite\0" "Date\0Wed, 15 Aug 2018 01:42:45 +0000\0" - "To\0linux-arm-kernel@lists.infradead.org\0" + "To\0dinguyen@kernel.org <dinguyen@kernel.org>" + robh+dt@kernel.org <robh+dt@kernel.org> + " airlied@linux.ie <airlied@linux.ie>\0" + "Cc\0linux-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>\0" "\00:1\0" "b\0" "On Tue, 2018-08-14 at 10:48 -0500, Dinh Nguyen wrote:\n" @@ -12,16 +22,16 @@ "> > \n" "> > From: Ong, Hean Loong <hean.loong.ong@intel.com>\n" "> > \n" - "> > The FPGA FrameBuffer Soft IP could be seen??as the GPU and the DRM\n" - "> > driver patch?\n" + "> > The FPGA FrameBuffer Soft IP could be seen\302\240\302\240as the GPU and the DRM\n" + "> > driver patch\302\240\n" "> > here is allocating memory for information to be streamed from the\n" - "> > ARM/Linux?\n" + "> > ARM/Linux\302\240\n" "> > to the display port. Basically the driver just wraps the\n" - "> > information such as?\n" + "> > information such as\302\240\n" "> > the pixels to be drawn by the FPGA FrameBuffer 2.\n" "> > \n" "> > The piece of hardware in discussion is the SoC FPGA where Linux\n" - "> > runs on the?\n" + "> > runs on the\302\240\n" "> > ARM chip and the FGPA is driven by its NIOS soft core with its own\n" "> > proprietary firmware.\n" "> This driver doesn't have to ARM specific does it?\n" @@ -29,42 +39,42 @@ "> > \n" "> > \n" "> > For example the application from the ARM Linux would have to write\n" - "> > information?\n" + "> > information\302\240\n" "> > on the /dev/fb0 with the information stored in the SDRAM to be\n" - "> > fetched by the?\n" + "> > fetched by the\302\240\n" "> > FPGA framebuffer IP and displayed on the Display Port Monitor.\n" "> > \n" "> > \n" "> > Ong Hean Loong (2):\n" - "> > ? ARM:socfpga-defconfig Intel FPGA Video and Image Processing Suite\n" - "> > ? ARM:drm ivip Intel FPGA Video and Image Processing Suite\n" + "> > \302\240 ARM:socfpga-defconfig Intel FPGA Video and Image Processing Suite\n" + "> > \302\240 ARM:drm ivip Intel FPGA Video and Image Processing Suite\n" "> > \n" "> > Ong, Hean Loong (1):\n" - "> > ? ARM:dt-bindings:display Intel FPGA Video and Image Processing\n" + "> > \302\240 ARM:dt-bindings:display Intel FPGA Video and Image Processing\n" "> > Suite\n" "> > \n" - "> > ?.../devicetree/bindings/display/altr,vip-fb2.txt???|???63 +++++++\n" - "> > ?arch/arm/configs/socfpga_defconfig?????????????????|????5 +\n" - "> > ?drivers/gpu/drm/Kconfig????????????????????????????|????2 +\n" - "> > ?drivers/gpu/drm/Makefile???????????????????????????|????1 +\n" - "> > ?drivers/gpu/drm/ivip/Kconfig???????????????????????|???14 ++\n" - "> > ?drivers/gpu/drm/ivip/Makefile??????????????????????|????9 +\n" - "> > ?drivers/gpu/drm/ivip/intel_vip_conn.c??????????????|???95\n" + "> > \302\240.../devicetree/bindings/display/altr,vip-fb2.txt\302\240\302\240\302\240|\302\240\302\240\302\24063 +++++++\n" + "> > \302\240arch/arm/configs/socfpga_defconfig\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240|\302\240\302\240\302\240\302\2405 +\n" + "> > \302\240drivers/gpu/drm/Kconfig\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240|\302\240\302\240\302\240\302\2402 +\n" + "> > \302\240drivers/gpu/drm/Makefile\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240|\302\240\302\240\302\240\302\2401 +\n" + "> > \302\240drivers/gpu/drm/ivip/Kconfig\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240|\302\240\302\240\302\24014 ++\n" + "> > \302\240drivers/gpu/drm/ivip/Makefile\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240|\302\240\302\240\302\240\302\2409 +\n" + "> > \302\240drivers/gpu/drm/ivip/intel_vip_conn.c\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240|\302\240\302\240\302\24095\n" "> > ++++++++++\n" - "> > ?drivers/gpu/drm/ivip/intel_vip_core.c??????????????|??161\n" + "> > \302\240drivers/gpu/drm/ivip/intel_vip_core.c\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240|\302\240\302\240161\n" "> > ++++++++++++++++\n" - "> > ?drivers/gpu/drm/ivip/intel_vip_drv.h???????????????|???52 ++++++\n" - "> > ?drivers/gpu/drm/ivip/intel_vip_of.c????????????????|??193\n" + "> > \302\240drivers/gpu/drm/ivip/intel_vip_drv.h\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240|\302\240\302\240\302\24052 ++++++\n" + "> > \302\240drivers/gpu/drm/ivip/intel_vip_of.c\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240\302\240|\302\240\302\240193\n" "> > ++++++++++++++++++++\n" - "> > ?10 files changed, 595 insertions(+), 0 deletions(-)\n" - "> > ?create mode 100644\n" + "> > \302\24010 files changed, 595 insertions(+), 0 deletions(-)\n" + "> > \302\240create mode 100644\n" "> > Documentation/devicetree/bindings/display/altr,vip-fb2.txt\n" - "> > ?create mode 100644 drivers/gpu/drm/ivip/Kconfig\n" - "> > ?create mode 100644 drivers/gpu/drm/ivip/Makefile\n" - "> > ?create mode 100644 drivers/gpu/drm/ivip/intel_vip_conn.c\n" - "> > ?create mode 100644 drivers/gpu/drm/ivip/intel_vip_core.c\n" - "> > ?create mode 100644 drivers/gpu/drm/ivip/intel_vip_drv.h\n" - "> > ?create mode 100644 drivers/gpu/drm/ivip/intel_vip_of.c\n" + "> > \302\240create mode 100644 drivers/gpu/drm/ivip/Kconfig\n" + "> > \302\240create mode 100644 drivers/gpu/drm/ivip/Makefile\n" + "> > \302\240create mode 100644 drivers/gpu/drm/ivip/intel_vip_conn.c\n" + "> > \302\240create mode 100644 drivers/gpu/drm/ivip/intel_vip_core.c\n" + "> > \302\240create mode 100644 drivers/gpu/drm/ivip/intel_vip_drv.h\n" + "> > \302\240create mode 100644 drivers/gpu/drm/ivip/intel_vip_of.c\n" "> > \n" "> Can you clarify your commit header? What is \"PATCH10\", is it version\n" "> 10?\n" @@ -77,4 +87,4 @@ "\n" > Dinh -ec39daa35e22d4bc204533010d83d50368bfbc106daa5f4a426eaab01fcc7751 +1a3074b7eebbebe6fed6cd919ed8b8c00237dd6ea40a9eb3e39ac7a885bc94e9
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.