From: Lucas De Marchi <lucas.demarchi@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>,
Paulo Zanoni <paulo.r.zanoni@intel.com>,
dri-devel@freedesktop.org
Subject: [PATCH libdrm v3 0/5] intel: rework how we add PCI IDs
Date: Wed, 5 Sep 2018 11:31:55 -0700 [thread overview]
Message-ID: <20180905183200.18383-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.
v2: address comments from Chris by pulling it out to a separate .c
v3: remove/add comments on first patch and rebase the rest
Discussed on v2 but left for later:
- replace intel_is_genx() with a simple check for bufmgr->gen,
after making sure said variable is initialized on all code
paths.
- treat unknown gen as a future gen
- convert gen < 9 to use the new header
Lucas De Marchi (5):
intel: add generic functions to check PCI ID
intel: make gen11 use generic gen macro
intel: make gen10 use generic gen macro
intel: make gen9 use generic gen macro
intel: get gen once for gen >= 9
intel/Makefile.sources | 1 +
intel/i915_pciids.h | 461 +++++++++++++++++++++++++++++++++++++++
intel/intel_bufmgr_gem.c | 8 +-
intel/intel_chipset.c | 85 ++++++++
intel/intel_chipset.h | 253 +--------------------
intel/intel_decode.c | 8 +-
intel/meson.build | 2 +-
7 files changed, 561 insertions(+), 257 deletions(-)
create mode 100644 intel/i915_pciids.h
create mode 100644 intel/intel_chipset.c
--
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-09-05 18:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-05 18:31 Lucas De Marchi [this message]
2018-09-05 18:31 ` [PATCH libdrm v3 1/5] intel: add generic functions to check PCI ID Lucas De Marchi
2018-09-05 18:31 ` [PATCH libdrm v3 2/5] intel: make gen11 use generic gen macro Lucas De Marchi
2018-09-05 18:31 ` [PATCH libdrm v3 3/5] intel: make gen10 " Lucas De Marchi
2018-09-05 18:31 ` [PATCH libdrm v3 4/5] intel: make gen9 " Lucas De Marchi
2018-09-05 18:32 ` [PATCH libdrm v3 5/5] intel: get gen once for gen >= 9 Lucas De Marchi
2018-09-05 19:56 ` [PATCH libdrm v3 0/5] intel: rework how we add PCI IDs Chris Wilson
2018-09-05 23:15 ` Rodrigo Vivi
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=20180905183200.18383-1-lucas.demarchi@intel.com \
--to=lucas.demarchi@intel.com \
--cc=dri-devel@freedesktop.org \
--cc=intel-gfx@lists.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 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.