[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <201006111044.42520.yannick.roehlly@free.fr>
Date: Fri, 11 Jun 2010 10:44:42 +0200
From: Yannick Roehlly <yannick.roehlly@...e.fr>
To: Bjorn Helgaas <bjorn.helgaas@...com>
Cc: Yinghai Lu <yinghai.lu@...cle.com>,
Jesse Barnes <jbarnes@...tuousgeek.org>,
"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -v2] pci: clear bridge resource size if BIOS assign bad one
Le Thursday 10 June 2010 01:30:31 Bjorn Helgaas, vous avez écrit :
> On Tuesday, June 08, 2010 05:36:33 pm Yinghai Lu wrote:
> > 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.
>
> I don't have the machine and can't be 100% sure, but based on what
> Yannic reported here:
> https://bugzilla.kernel.org/show_bug.cgi?id=16009#c11, it looks like
> Windows moved that aperture.
>
> I haven't used it myself, but possibly a program like SIV
> (http://rh-software.com/) would give more detailed information
> about what Windows is doing.
Hi Bjorn,
I don't know if it's useful, but here some output of SIV concerning PCI and
the Radeon card.
Yannick
View attachment "siv_output_1.txt" of type "text/plain" (6116 bytes)
Powered by blists - more mailing lists