Quoting De Marchi, Lucas (2017-12-20 20:06:24) > 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. We did that, it's called i915_pciids.h. We said we would put all the ids into a single header in a format that both userspace and the kernel could digest, then copy it wherever required. It's just a cp; git commit. The difficult part is then tying the pci-id to the internal db of the project, and our proposal to share that was shot down. -Chris _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
