intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
* [PATCH i-g-t 0/3] Various fixes for non-Intel compatibility
@ 2016-11-21 22:32 Lyude
  2016-11-21 22:32 ` [PATCH i-g-t 1/3] igt_kms: Don't assume we have cursor planes if we have primary ones Lyude
                   ` (2 more replies)
  0 siblings, 3 replies; 6+ messages in thread
From: Lyude @ 2016-11-21 22:32 UTC (permalink / raw)
  To: intel-gfx; +Cc: Lyude

Here's a couple of fixes I ended up needing when I was working on trying to get
the chamelium tests to pass on the other GPUs I've got available. This should
make both igt_display_init() and kmstest_force_connector() work properly on
most non-intel hardware.

Lyude (3):
  igt_kms: Don't assume we have cursor planes if we have primary ones
  igt_kms: Change the max number of pipes to 6
  igt_kms: Don't require intel hardware for kmstest_force_connector

 lib/igt_kms.c | 50 +++++++++++++++++++++++++++++---------------------
 lib/igt_kms.h | 23 ++++++++++++++++++++---
 2 files changed, 49 insertions(+), 24 deletions(-)

-- 
2.7.4

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2016-12-07  7:34 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-11-21 22:32 [PATCH i-g-t 0/3] Various fixes for non-Intel compatibility Lyude
2016-11-21 22:32 ` [PATCH i-g-t 1/3] igt_kms: Don't assume we have cursor planes if we have primary ones Lyude
2016-12-07  7:34   ` Tomeu Vizoso
2016-11-21 22:32 ` [PATCH i-g-t 2/3] igt_kms: Change the max number of pipes to 6 Lyude
2016-12-07  7:26   ` Tomeu Vizoso
2016-11-21 22:32 ` [PATCH i-g-t 3/3] igt_kms: Don't require intel hardware for kmstest_force_connector Lyude

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).