public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Damien Lespiau <damien.lespiau@intel.com>
To: Emil Velikov <emil.l.velikov@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH libdrm 00/12] Introduce drm_intel_device and use i915_pciid.h
Date: Fri, 6 Mar 2015 14:35:29 +0000	[thread overview]
Message-ID: <20150306143529.GD14976@strange.config> (raw)
In-Reply-To: <54F9B564.3070308@gmail.com>

On Fri, Mar 06, 2015 at 02:10:44PM +0000, Emil Velikov wrote:
> On 05/03/15 16:20, Damien Lespiau wrote:
> > A couple of things I wanted to do for the longest time:
> >   
> >   - Have (intel's) libdrm use the kernel i915_pciids.h so we can just copy the
> >     file when updating
> >   - Start a new object, struct drm_intel_device where we could put common code
> >     across several userspace projects. For instance it could be where we put
> >     the "number of threads" logic we need to use in several 3d/gpgpu
> >     states/instructions (that's a bit fiddly starting with CHV: we can't use
> >     static tables anymore and need a runtime query to the kernel)
> > 
> Hi Damien,
> 
> So this paves the way to de-duplicate the device information stored in
> beignet, libva-intel-driver, mesa, xf86-video-intel, other ?

I don't expect xf86-video-intel to use this, but otherwise that's the
long term plan (will need a lot more work though).

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

      reply	other threads:[~2015-03-06 14:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-05 16:20 [PATCH libdrm 00/12] Introduce drm_intel_device and use i915_pciid.h Damien Lespiau
2015-03-05 16:20 ` [PATCH 01/12] intel: Remove unused define IS_MOBILE() Damien Lespiau
2015-03-05 16:20 ` [PATCH 02/12] intel: Introduce an drm_intel_device object Damien Lespiau
2015-03-05 16:20 ` [PATCH 03/12] intel: Use drm_intel_device in the gem buffer manager Damien Lespiau
2015-03-05 16:20 ` [PATCH 04/12] intel: Make drm_intel_decode use a drm_intel_device Damien Lespiau
2015-03-05 16:20 ` [PATCH 05/12] intel: Use '||' for the boolean or Damien Lespiau
2015-03-05 16:20 ` [PATCH 06/12] intel: Kill the IS_9XX() macro Damien Lespiau
2015-03-05 16:20 ` [PATCH 07/12] intel: Kill the IS_GEN4() macro Damien Lespiau
2015-03-05 16:20 ` [PATCH 08/12] intel: Remove direct usage of IS_915() Damien Lespiau
2015-03-05 16:20 ` [PATCH 09/12] intel: Provide IS_GENX() macros taking a drm_intel_device as argument Damien Lespiau
2015-03-05 18:41   ` Ian Romanick
2015-03-05 18:45     ` Damien Lespiau
2015-03-05 16:20 ` [PATCH 10/12] intel: Make test_decode fail gracefully the decode context is NULL Damien Lespiau
2015-03-05 16:20 ` [PATCH 11/12] intel: Make test_decode not depend on intel_chipset.h Damien Lespiau
2015-03-05 16:20 ` [PATCH 12/12] intel: Remove intel_chipset.h Damien Lespiau
2015-03-05 18:44 ` [PATCH libdrm 00/12] Introduce drm_intel_device and use i915_pciid.h Ian Romanick
2015-03-06 14:10 ` Emil Velikov
2015-03-06 14:35   ` Damien Lespiau [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=20150306143529.GD14976@strange.config \
    --to=damien.lespiau@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emil.l.velikov@gmail.com \
    --cc=intel-gfx@lists.freedesktop.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