public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Jesse Barnes <jesse.barnes@intel.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
	Greg KH <gregkh@suse.de>, Adam Jackson <ajackson@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: PCI bridge range sizing bug
Date: Sat, 21 Apr 2007 01:31:38 -0400	[thread overview]
Message-ID: <4629A1BA.1020400@redhat.com> (raw)
In-Reply-To: <200704201334.56802.jesse.barnes@intel.com>

Jesse Barnes wrote:
> On Friday, April 20, 2007 11:28 am Linus Torvalds wrote:
>> On Fri, 20 Apr 2007, Jesse Barnes wrote:
>>> Sounds good, hopefully reassigning the bridge resources won't cause
>>> too much trouble.  Do you have time to hack this up?  If not, I
>>> could give it a try, as long as ajax is willing to test...
>> Actually, I would suggest we not do it automatically (because the
>> need for it is just so low, and the downsides are potentially huge -
>> there are just too many resources that are "hidden" from us through
>> ACPI tricks and having hardware that doesn't actually expose their
>> PCI resources fully through the normal PCI resource setup).
> 
> Yeah, that's probably prudent.  OTOH we should probably let the user 
> know in no uncertain terms that some of the stuff behind one of their 
> bridges will be inaccessible.

Something like that would have made it a lot more obvious
why my Matrox PCIe x1 video card will not work in my Dell
9150, while a PCI video card does work.

The PCI video card directly sits on the bus, and gets its
resources assigned by the BIOS.

The PCIe video card turned out to be a PCIe to AGP bridge,
and the BIOS did not assign the needed PCI resources, making
the system crash when I started X.

X seemed to have some trouble reading the ROM, too...

-- 
Politics is the struggle between those who want to make their country
the best in the world, and those who believe it already is.  Each group
calls the other unpatriotic.

      reply	other threads:[~2007-04-21  5:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1175812632.17147.12.camel@localhost.localdomain>
2007-04-19 23:11 ` PCI bridge range sizing bug Jesse Barnes
2007-04-19 23:40   ` Greg KH
2007-04-20  0:19     ` Linus Torvalds
2007-04-20  9:23       ` Ivan Kokshaysky
2007-04-20 16:32         ` Jesse Barnes
2007-04-20 18:28           ` Linus Torvalds
2007-04-20 20:30             ` Ivan Kokshaysky
2007-05-14 17:45               ` Jesse Barnes
2007-05-15 22:39                 ` Ivan Kokshaysky
2007-04-20 20:34             ` Jesse Barnes
2007-04-21  5:31               ` Rik van Riel [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=4629A1BA.1020400@redhat.com \
    --to=riel@redhat.com \
    --cc=ajackson@redhat.com \
    --cc=gregkh@suse.de \
    --cc=ink@jurassic.park.msu.ru \
    --cc=jesse.barnes@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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