From: Jani Nikula <jani.nikula@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
Chris Wilson <chris@chris-wilson.co.uk>,
Intel-gfx@lists.freedesktop.org
Cc: Lucas De Marchi <lucas.demarchi@intel.com>,
Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH 4/4] drm/i915: Introduce concept of a sub-platform
Date: Wed, 27 Mar 2019 17:06:58 +0200 [thread overview]
Message-ID: <87tvfo2w6l.fsf@intel.com> (raw)
In-Reply-To: <3b11ccb1-6c0b-4a28-f388-f17594a63a63@linux.intel.com>
On Wed, 27 Mar 2019, Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com> wrote:
> On 27/03/2019 12:03, Jani Nikula wrote:
>> A lot of this could go away if we were able to encode a bunch of the
>> flags in a single array similar to pciidtable.
>
> I don't see how we can encode everything to distinguish a platform in an
> unsigned long, not even on 64-bit?
Me neither. That's why I'm blabbering here instead of writing a
patch. :p
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-03-27 15:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 7:40 [PATCH 0/4] Device id consolidation Tvrtko Ursulin
2019-03-26 7:40 ` [PATCH 1/4] drm/i915: Split Pineview device info into desktop and mobile Tvrtko Ursulin
2019-03-26 7:40 ` [PATCH 2/4] drm/i915: Remove redundant device id from IS_IRONLAKE_M macro Tvrtko Ursulin
2019-03-26 7:40 ` [PATCH 3/4] drm/i915: Split some PCI ids into separate groups Tvrtko Ursulin
2019-03-26 7:40 ` [PATCH 4/4] drm/i915: Introduce concept of a sub-platform Tvrtko Ursulin
2019-03-26 8:39 ` Jani Nikula
2019-03-26 9:34 ` Jani Nikula
2019-03-26 9:53 ` Chris Wilson
2019-03-27 11:35 ` Tvrtko Ursulin
2019-03-27 11:41 ` Chris Wilson
2019-03-27 12:03 ` Jani Nikula
2019-03-27 14:33 ` Tvrtko Ursulin
2019-03-27 15:06 ` Jani Nikula [this message]
2019-03-27 11:37 ` Tvrtko Ursulin
2019-03-27 14:23 ` [PATCH v8 " Tvrtko Ursulin
2019-03-29 9:54 ` Jani Nikula
2019-03-29 12:10 ` Tvrtko Ursulin
2019-03-29 13:10 ` Jani Nikula
2019-03-26 15:59 ` ✗ Fi.CI.CHECKPATCH: warning for Device id consolidation Patchwork
2019-03-26 16:01 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-03-26 16:19 ` ✓ Fi.CI.BAT: success " Patchwork
2019-03-26 23:06 ` ✗ Fi.CI.IGT: failure " Patchwork
2019-03-27 17:52 ` ✗ Fi.CI.CHECKPATCH: warning for Device id consolidation (rev2) Patchwork
2019-03-27 17:54 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-03-27 18:38 ` ✓ Fi.CI.BAT: success " Patchwork
2019-04-01 16:18 ` Tvrtko Ursulin
2019-03-28 9:23 ` [PATCH 0/4] Device id consolidation Tvrtko Ursulin
2019-03-28 9:39 ` Chris Wilson
2019-03-29 9:17 ` Tvrtko Ursulin
2019-03-28 12:43 ` ✓ Fi.CI.IGT: success for Device id consolidation (rev2) Patchwork
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=87tvfo2w6l.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=lucas.demarchi@intel.com \
--cc=paulo.r.zanoni@intel.com \
--cc=tvrtko.ursulin@linux.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