From: "Dave Airlie" <airlied@gmail.com>
To: "Linus Torvalds" <torvalds@osdl.org>
Cc: "Andrew Morton" <akpm@osdl.org>,
"Matthew Reppert" <arashi@sacredchao.net>,
linux-kernel@vger.kernel.org, "Dave Airlie" <airlied@linux.ie>,
"Antonino A. Daplas" <adaplas@pol.net>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>
Subject: Re: PCI ROM resource allocation issue with 2.6.17-rc2
Date: Wed, 26 Apr 2006 15:56:01 +1000 [thread overview]
Message-ID: <21d7e9970604252256m7192ffeboa47c890fef4e4623@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0604252158460.3701@g5.osdl.org>
>
> Note that the "transparent" really means that it forwards all IO resources
> even outside the windows, and the windows are really just for show.
>
> The kernel even used to totally ignore them, now it uses them as a hint
> and will _preferably_ put stuff inside the window for such bridges, if the
> windows have been set up (not all systems will even set up the windows at
> all).
Well X has support for it, but something like the quirk in the i386
fixups is needed to make it detect the Intel PCI bridge as a
transparent one..
> >
>
> It really shouldn't even matter where it ends up being enabled. Trying to
> move it into the bridge window is as good as anything else, since it was
> disabled to begin with (which means that you can't necessarily trust the
> location that it was disabled _at_ - the ffff0000 value could even be just
> what the firmware left it at after doing PCI BAR sizing, although I
> suspect that it's a perfectly valid address).
Well it does, as modprobing the DRM enables the device, and we store
the values in the DRM, X then goes and moves it... and the drm gets
annoyed later,
I still haven't tracked down the problem with the BIOS but I'm on its
trail now that I've fixed the PCI resource allocation..
Dave.
next prev parent reply other threads:[~2006-04-26 5:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-24 4:02 PCI ROM resource allocation issue with 2.6.17-rc2 Matthew Reppert
2006-04-24 5:21 ` Andrew Morton
2006-04-24 5:54 ` Dave Airlie
2006-04-24 17:07 ` Linus Torvalds
2006-04-24 17:16 ` Arjan van de Ven
2006-04-24 17:28 ` Linus Torvalds
2006-04-26 1:23 ` Dave Airlie
2006-04-26 2:10 ` Jon Smirl
2006-04-24 17:01 ` Linus Torvalds
2006-04-26 3:28 ` Dave Airlie
2006-04-26 3:40 ` Debian Kernel with Squash and UnionFS installed Joshua Perrymon
2006-04-26 5:05 ` PCI ROM resource allocation issue with 2.6.17-rc2 Linus Torvalds
2006-04-26 5:56 ` Dave Airlie [this message]
2006-04-24 5:28 ` Matthew Reppert
2006-04-24 19:24 ` Jon Smirl
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=21d7e9970604252256m7192ffeboa47c890fef4e4623@mail.gmail.com \
--to=airlied@gmail.com \
--cc=adaplas@pol.net \
--cc=airlied@linux.ie \
--cc=akpm@osdl.org \
--cc=arashi@sacredchao.net \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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