From: Lucas De Marchi <lucas.demarchi@intel.com>
To: intel-gfx@freedesktop.org, dri-devel@freedesktop.org
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: [PATCH libdrm 0/4] intel: rework how we add PCI IDs
Date: Fri, 24 Aug 2018 16:56:45 -0700 [thread overview]
Message-ID: <20180824235649.19444-1-lucas.demarchi@intel.com> (raw)
Adding PCI IDs to different projects is a boring manual task that
motivated me to create this series. The idea is to centralize the IDs in
the kernel header and let other projects copy it.
Initially my plan was to convert all gens, back to gen2, but that proved
slightly difficult since there are some corner cases to cover and I
didn't want to block the important part, i.e.: for recent gens, there's
no risk of missing a PCI ID.
It does increase the size a little bit, but doesn't explode. Size diff
below showing ~3k:
- 36533 176 40 36749 8f8d build/intel/intel@@drm_intel@sha/intel_bufmgr_gem.c.o
- 66237 1384 24 67645 1083d build/intel/intel@@drm_intel@sha/intel_decode.c.o
+ 39362 176 40 39578 9a9a build/intel/intel@@drm_intel@sha/intel_bufmgr_gem.c.o
+ 68935 1384 24 70343 112c7 build/intel/intel@@drm_intel@sha/intel_decode.c.o
Let me know what you think.
Lucas De Marchi (4):
intel: add IS_GENX() generic macro
intel: make gen11 use generic gen macro
intel: make gen10 use generic gen macro
intel: make gen9 use generic gen macro
intel/i915_pciids.h | 461 ++++++++++++++++++++++++++++++++++++++++++
intel/intel_chipset.h | 267 +++---------------------
2 files changed, 487 insertions(+), 241 deletions(-)
create mode 100644 intel/i915_pciids.h
--
2.17.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-08-24 23:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-24 23:56 Lucas De Marchi [this message]
2018-08-24 23:56 ` [PATCH libdrm 1/4] intel: add IS_GENX() generic macro Lucas De Marchi
2018-08-25 9:35 ` Chris Wilson
2018-08-27 21:19 ` Lucas De Marchi
2018-08-27 21:40 ` Chris Wilson
2018-08-27 23:15 ` Lucas De Marchi
2018-08-28 1:00 ` Lucas De Marchi
2018-08-28 8:38 ` Chris Wilson
2018-08-28 16:16 ` Lucas De Marchi
2018-08-24 23:56 ` [PATCH libdrm 2/4] intel: make gen11 use generic gen macro Lucas De Marchi
2018-08-24 23:56 ` [PATCH libdrm 3/4] intel: make gen10 " Lucas De Marchi
2018-08-24 23:56 ` [PATCH libdrm 4/4] intel: make gen9 " Lucas De Marchi
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=20180824235649.19444-1-lucas.demarchi@intel.com \
--to=lucas.demarchi@intel.com \
--cc=dri-devel@freedesktop.org \
--cc=intel-gfx@freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=rodrigo.vivi@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).