dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Bruno Wolff III <bruno@wolff.to>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: David Airlie <airlied@linux.ie>,
	daniel.vetter@ffwll.ch, intel-gfx@lists.freedesktop.org,
	"open list:INTEL DRM DRIVERS (excluding Poulsbo, Moorestow...),
	linux-kernel@vger.kernel.org (open list)"
	<dri-devel@lists.freedesktop.org>,
	Daniel Vetter <daniel.vetter@intel.com>,
	bjorn@mork.no
Subject: Re: [PATCH v2] drm/i915: refine qemu south bridge detection
Date: Thu, 28 Jan 2016 10:07:44 -0600	[thread overview]
Message-ID: <20160128160744.GA9289@wolff.to> (raw)
In-Reply-To: <1453719748-10944-1-git-send-email-kraxel@redhat.com>

On Mon, Jan 25, 2016 at 12:02:28 +0100,
  Gerd Hoffmann <kraxel@redhat.com> wrote:
>The test for the qemu q35 south bridge added by commit
>"39bfcd52 drm/i915: more virtual south bridge detection"
>also matches on real hardware.  Having the check for
>virtual systems last in the list is not enough to avoid
>that ...
>
>Refine the check by additionally verifying the pci
>subsystem id to see whenever it *really* is qemu.
>
>[ v2: fix subvendor tyops ]

I haven't seen this patch (or a revert of 39bfcd52) show up in the intel 
drm repos yet. Has anyone asked for this tpo be included? Is there some 
problem with the patch? (It works for me.)
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2016-01-28 16:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-25 11:02 [PATCH v2] drm/i915: refine qemu south bridge detection Gerd Hoffmann
2016-01-26  8:57 ` Bruno Wolff III
2016-01-28 16:07 ` Bruno Wolff III [this message]
2016-01-29  7:06   ` Jani Nikula
2016-01-29  7:59 ` Jani Nikula
2016-01-29  8:49   ` Gerd Hoffmann
2016-01-29  9:03     ` Jani Nikula

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=20160128160744.GA9289@wolff.to \
    --to=bruno@wolff.to \
    --cc=airlied@linux.ie \
    --cc=bjorn@mork.no \
    --cc=daniel.vetter@ffwll.ch \
    --cc=daniel.vetter@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kraxel@redhat.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).