qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Igor Mammedov <imammedo@redhat.com>
To: qemu-devel@nongnu.org
Cc: mst@redhat.com, stefanb@us.ibm.com, crobinso@redhat.com
Subject: [Qemu-devel] [PATCH for-2.6 v2 0/2] acpi: tpm: "Fix" TPM ACPI description
Date: Fri,  8 Apr 2016 13:23:12 +0200	[thread overview]
Message-ID: <1460114594-236342-1-git-send-email-imammedo@redhat.com> (raw)

TPM used to 'work', since in commit:
  711b20b4 Add ACPI tables for TPM
as TPM device has been placed outside of PCI0 bus scope
with IRQ commented out, but since commit
  5cb18b3d TPM2 ACPI table support
with following fixup
  9e472263 acpi: add missing ssdt
it has been moved to correct ISA bus scope,
however no one added MMIO resource to parent bus
and IRQ(5) became uncommented which regressed
TPM as Windows fails to init it due to lack of resources
  'device cannot find enough free resources'

Series is a partialy fix and a partially hack to
temporary make TPM work on Windows.
 1/2 - fixes IO resource lack on parent bus
 2/2 - temporary comment out IRQ description
       to make Windows beleve that there isn't
       any possible conflict to force successful
       driver initialization

Tested with Windows 8.1x64

Igor Mammedov (2):
  pc: acpi: tpm: add missing MMIO resource to PCI0._CRS
  tpm: acpi: remove IRQ from TPM's CRS to make Windows not see conflict

 hw/i386/acpi-build.c | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

-- 
1.8.3.1

             reply	other threads:[~2016-04-08 11:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-08 11:23 Igor Mammedov [this message]
2016-04-08 11:23 ` [Qemu-devel] [PATCH for-2.6 v2 1/2] pc: acpi: tpm: add missing MMIO resource to PCI0._CRS Igor Mammedov
2016-04-08 11:23 ` [Qemu-devel] [PATCH for-2.6 v2 2/2] tpm: acpi: remove IRQ from TPM's CRS to make Windows not see conflict Igor Mammedov

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=1460114594-236342-1-git-send-email-imammedo@redhat.com \
    --to=imammedo@redhat.com \
    --cc=crobinso@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanb@us.ibm.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).