linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
	linux-kernel@vger.kernel.org, Thomas Renninger <trenn@suse.de>
Subject: Re: [PATCH] x86/PCI: parse additional host bridge window resource types
Date: Thu, 22 Apr 2010 16:17:49 -0700	[thread overview]
Message-ID: <20100422161749.5e8af128@virtuousgeek.org> (raw)
In-Reply-To: <20100420195241.13265.93577.stgit@bob.kio>

On Tue, 20 Apr 2010 13:52:41 -0600
Bjorn Helgaas <bjorn.helgaas@hp.com> wrote:

> 
> This adds support for Memory24, Memory32, and Memory32Fixed descriptors in
> PCI host bridge _CRS.
> 
> I experimentally determined that Windows (2008 R2) accepts these descriptors
> and treats them as windows that are forwarded to the PCI bus, e.g., if
> it finds any PCI devices with BARs outside the windows, it moves them into
> the windows.
> 
> I don't know whether any machines actually use these descriptors in PCI
> host bridge _CRS methods, but if any exist and they're new enough that we
> automatically turn on "pci=use_crs", they will work with Windows but not
> with Linux.
> 
> Here are the details: https://bugzilla.kernel.org/show_bug.cgi?id=15817
> 
> Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
> ---

Applied to for-linus, thanks.

-- 
Jesse Barnes, Intel Open Source Technology Center

      reply	other threads:[~2010-04-22 23:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-20 19:52 [PATCH] x86/PCI: parse additional host bridge window resource types Bjorn Helgaas
2010-04-22 23:17 ` Jesse Barnes [this message]

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=20100422161749.5e8af128@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=bjorn.helgaas@hp.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=trenn@suse.de \
    /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).