mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Haiyang Zhang <haiyangz@microsoft.com>
Cc: Hank Janssen <hjanssen@microsoft.com>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Problem with auto-detecting a HV environment from within Linux
Date: Thu, 25 Feb 2010 16:21:12 -0800	[thread overview]
Message-ID: <20100226002112.GB30698@kroah.com> (raw)
In-Reply-To: <1FB5E1D5CA062146B38059374562DF725B6A5806@TK5EX14MBXC130.redmond.corp.microsoft.com>

On Thu, Feb 25, 2010 at 11:40:52PM +0000, Haiyang Zhang wrote:
> > -----Original Message-----
> > From: Greg KH [mailto:greg@kroah.com]
> > Sent: Thursday, February 25, 2010 6:07 PM
> > If so, what is the vendor and product id of this device?
> 
> The Vendor:Device Id is: 1414:5353
> 00:08.0 VGA compatible controller [0300]: Microsoft Corporation Device [1414:5353]
> 
> This hasn't been changed since the first release of HyperV. I will ask
> around about the future stability of the VGA card (and the DMI).

Thanks for the device id.

I'll make up a patch for testing now, as we should be able to just
trigger on this pci device id, and do the dmi test to be "safe" as well.
Any future changes can easily be added to the tables.

thanks,

greg k-h

  reply	other threads:[~2010-02-26  0:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-25 16:44 Greg KH
2010-02-25 17:30 ` Haiyang Zhang
2010-02-25 17:36   ` Greg KH
2010-02-25 18:37     ` Haiyang Zhang
2010-02-25 23:06       ` Greg KH
2010-02-25 23:40         ` Haiyang Zhang
2010-02-26  0:21           ` Greg KH [this message]
2010-02-26  0:46           ` Greg KH
2010-02-26  2:14             ` Hank Janssen
2010-02-26  2:57               ` Greg KH
2010-02-26 19:07                 ` Haiyang Zhang
2010-02-26 19:16                   ` Greg KH
2010-02-26  9:47             ` Ameya Palande
2010-02-26 14:54               ` Greg KH

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=20100226002112.GB30698@kroah.com \
    --to=greg@kroah.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=haiyangz@microsoft.com \
    --cc=hjanssen@microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    /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
all inboxes | Powered by JetHome®