public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai.lu@oracle.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	Yannick Roehlly <yannick.roehlly@free.fr>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -v2] pci: clear bridge resource size if BIOS assign bad one
Date: Tue, 08 Jun 2010 16:36:33 -0700	[thread overview]
Message-ID: <4C0ED401.6060800@oracle.com> (raw)
In-Reply-To: <201006081649.00332.bjorn.helgaas@hp.com>

On 06/08/2010 03:48 PM, Bjorn Helgaas wrote:
> On Tuesday, June 08, 2010 03:43:50 pm Jesse Barnes wrote:

> 
> In this case, the aperture *size* from the BIOS is actually OK, but
> the beginning of the aperture overlaps system memory.  With Yinghai's
> patch, we reduce the size and move the start.  Windows was able to
> just move the start of the aperture and preserve the original
> 0x20000000 size (but I think it had to move something else out of
> the way).

are you sure? that looks more aggressive.

Yinghai

  reply	other threads:[~2010-06-08 23:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-16009-13546@https.bugzilla.kernel.org/>
     [not found] ` <201005191637.13177.bjorn.helgaas@hp.com>
     [not found]   ` <201005202236.20444.bjorn.helgaas@hp.com>
     [not found]     ` <201006021536.43333.bjorn.helgaas@hp.com>
     [not found]       ` <4C070ECA.2020309@oracle.com>
2010-06-03 20:43         ` [PATCH -v2] pci: clear bridge resource size if BIOS assign bad one Yinghai Lu
2010-06-03 23:02           ` Yannick Roehlly
2010-06-08 21:43           ` Jesse Barnes
2010-06-08 22:48             ` Bjorn Helgaas
2010-06-08 23:36               ` Yinghai Lu [this message]
2010-06-09 23:30                 ` Bjorn Helgaas
2010-06-11  8:44                   ` Yannick Roehlly
2010-06-11 22:45                     ` Bjorn Helgaas

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=4C0ED401.6060800@oracle.com \
    --to=yinghai.lu@oracle.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=yannick.roehlly@free.fr \
    /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