All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: Yao Cheng <yao.cheng@intel.com>
Cc: daniel.vetter@intel.com, intel-gfx@lists.freedesktop.org,
	fei.jiang@intel.com, dri-devel@lists.freedesktop.org
Subject: Re: [RFC PATCH 0/3] drm driver for baytrail's vxd392
Date: Tue, 14 Oct 2014 13:53:00 +0200	[thread overview]
Message-ID: <20141014115259.GD5057@ulmo> (raw)
In-Reply-To: <1413202502-19026-1-git-send-email-yao.cheng@intel.com>


[-- Attachment #1.1: Type: text/plain, Size: 784 bytes --]

On Mon, Oct 13, 2014 at 08:15:00PM +0800, Yao Cheng wrote:
> drm/ipvr is a new GEM driver for baytrail's vxd392, which accelerates VP8 video decoding.
> The driver name "ipvr" means the PowerVR's IP wrapped by Intel. In the future, ipvr may support other platforms such as Merrifield.
> Code is placed at drivers/gpu/drm/ipvr and the following two new Kconfig are added:
>   CONFIG_DRM_IPVR: Build option for ipvr module
>   CONFIG_DRM_IPVR_EC: Experimental feature of error concealment
> 
> User mode drm helper "libdrm_ipvr.so" and simple test are also included.
> 
> Yao Cheng (3):
>  [1/3] drm/i915: add vxd392 bridge in i915 on baytrail
>  [2/3] drm/ipvr: ipvr drm driver for vxd392

If this is Intel-specific, why doesn't it live under the i915 driver?

Thierry

[-- Attachment #1.2: Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2014-10-14 11:53 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-13 12:15 [RFC PATCH 0/3] drm driver for baytrail's vxd392 Yao Cheng
2014-10-13 12:15 ` [RFC PATCH 1/3] drm/i915: add vxd392 bridge in i915 Yao Cheng
2014-10-14 13:26   ` Jani Nikula
2014-10-15  2:02     ` [Intel-gfx] " Cheng, Yao
2014-10-16 10:15   ` Daniel Vetter
2014-10-16 15:05     ` Cheng, Yao
2014-10-19 11:27       ` Daniel Vetter
2014-10-13 12:15 ` [RFC PATCH 2/3] drm/ipvr: drm driver for vxd392 Yao Cheng
2014-10-13 14:26   ` David Herrmann
2014-10-15  2:14     ` Cheng, Yao
2014-10-16  9:46       ` David Herrmann
2014-10-16 10:28       ` Daniel Vetter
2014-10-16 13:39         ` [Intel-gfx] " Cheng, Yao
2014-10-16 13:47           ` David Herrmann
2014-10-19 11:28             ` Daniel Vetter
2014-10-14 11:53 ` Thierry Reding [this message]
2014-10-14 15:50   ` [Intel-gfx] [RFC PATCH 0/3] drm driver for baytrail's vxd392 Sean V Kelley
2014-10-15  2:04     ` Cheng, Yao
2014-10-15  8:13     ` [Intel-gfx] " Thierry Reding
2014-10-15  8:18       ` Stéphane Marchesin
2014-10-15  8:31         ` Thierry Reding
2014-10-16 10:34       ` [Intel-gfx] " Daniel Vetter
2014-10-16 18:42       ` Rob Clark
2014-10-17  0:40         ` Jiang, Fei
2014-10-16 11:45 ` Daniel Vetter
2014-10-16 14:36   ` [Intel-gfx] " Cheng, Yao
2014-10-16 16:26     ` Sean V Kelley

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=20141014115259.GD5057@ulmo \
    --to=thierry.reding@gmail.com \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fei.jiang@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=yao.cheng@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 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.