From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "De Marchi, Lucas" <lucas.demarchi@intel.com>,
"Rogozhkin, Dmitry V" <dmitry.v.rogozhkin@intel.com>
Cc: igt-dev@lists.freedesktop.org, mesa-dev@lists.freedesktop.org,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [igt-dev] [Intel-gfx] [PATCH i-g-t] lib/i915_pciids.h: synchronize with kernel header
Date: Tue, 5 Feb 2019 15:32:50 -0800 [thread overview]
Message-ID: <20190205233250.GA5704@intel.com> (raw)
In-Reply-To: <1513800381.12908.6.camel@intel.com>
Hi all,
restarting a very old thread since Dmitry is interested in tackle
the issue that we have to propagate and keep all IDs in sync across
the stack.
He has few ideas of i915 ioctls in a way that it wouldn't necessarily
tie build dependencies etc..
Since I believe this place is the best one to discuss ideas like that
let me invite him for the discussion in a way he can explain his
ideas here.
Also cc'ing some relevant mailing lists.
Thanks,
Rodrigo.
On Wed, Dec 20, 2017 at 12:06:24PM -0800, De Marchi, Lucas wrote:
> On Tue, 2017-12-19 at 15:28 -0800, Rodrigo Vivi wrote:
> > On Tue, Dec 19, 2017 at 10:07:30PM +0000, Chris Wilson wrote:
> > > Quoting Rodrigo Vivi (2017-12-19 21:59:43)
> > > > On Fri, Dec 08, 2017 at 10:06:46PM +0000, Lucas De Marchi wrote:
> > > > > This copies include/drm/i915_pciids.h from kernel as of drm-tip:
> > > > > drm-tip: 2017y-12m-08d-21h-06m-35s UTC + patch adding INTEL_CFL_IDS
> > > > > that
> > > > > was missing there[1].
> > > >
> > > > Since this tip name is not easily found maybe it would be good to
> > > > mention latest kernel commit that touched this file.
> > > >
> > > > > The goal is to keep track of the PCI IDs in a
> > > > > single place (kernel).
> > > >
> > > > good idea.
> > > >
> > > > >
> > > > > Right now a simple copy is done to catch up with latest changes there,
> > > > > although in future it could be more sofisticated pointing the build
> > > > > system to the external header.
> > > >
> > > > Yeap, a real single place would be awesome.
> > >
> > > Whilst maintaining independence of the igt build itself?
> >
> > yeap... nevermind...
> > I was just in another discussion about detection of cnl on vaapi driver
> > and I realized that the userspace individual detection has its advantages...
>
> I get the benefit of not tying i-g-t to particular kernel versions, but we may
> need to think in a way to alleviate the tedious work of updating the IDs
> across the projects.
>
> Some alternatives:
>
> 1) Move header to e.g. include/external/i915_pciids.h and add a
> scripts/i915-update-ids that receives the kernel directory as argument. The
> script does whateve is needed to update the header, which may or may not
> include adding a verbiage on top of the header
>
> /* This header is automatically generated, do not edit it */
>
> 2) Just create a policy that changes to this header needs to actually be a
> copy from the kernel header with the commit hash in the commit message
>
> 3) A mix or partial implementation of (1) and (2).
>
> What do you think?
>
> Lucas De Marchi
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
parent reply other threads:[~2019-02-05 23:32 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1513800381.12908.6.camel@intel.com>]
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=20190205233250.GA5704@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=dmitry.v.rogozhkin@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=mesa-dev@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