From: Tony Camuso <tcamuso@redhat.com>
To: Robert Hancock <hancockr@shaw.ca>
Cc: Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz,
"Chumbalkar, Nagananda" <Nagananda.Chumbalkar@hp.com>
Subject: Re: [Fwd: Re: [PATCH 0/5]PCI: x86 MMCONFIG]
Date: Thu, 20 Dec 2007 21:09:52 -0500 [thread overview]
Message-ID: <476B2070.7020004@redhat.com> (raw)
In-Reply-To: <476B0C58.4030703@shaw.ca>
Robert Hancock wrote:
> The case of the device built into the K8 northbridge that's unreachable
> by MMCONFIG kind of makes sense, since the northbridge is what's
> translating the MMCONFIG memory access into config accesses. It seems
> bizarre to me that a bridge chip could possibly have such a problem. The
> MMCONFIG access should get translated into a configuration space access
> in the northbridge and from that point on there's no difference between
> an MMCONFIG and type1 access.
>
Robert's point is well taken.
Only northbridge chips can give us this kind of trouble, and the only
chips mentioned in the present discussion as not being mmconf-compliant
are northbridges (8132, ht1000).
The patch is aware of this, so once a root bus has been programmed for
legacy pci config access, all descendent buses automatically inherit
this access mechanism and are therefore not probed by the patch.
next prev parent reply other threads:[~2007-12-21 2:11 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.HvUNJ45qy60H427u0v9fNt3Gc7E@ifi.uio.no>
[not found] ` <fa.uuzqvr64HFsgxfiWwhEmE16Di6c@ifi.uio.no>
[not found] ` <fa.zhxdNN/1rfQhfJLVmdGBjvKYrCM@ifi.uio.no>
[not found] ` <fa.z1qlON6DA9ubBPFdrEcaFTMgYOY@ifi.uio.no>
[not found] ` <fa.U/SCC1Gvd3nSOpkMu5vcsSPYyPE@ifi.uio.no>
[not found] ` <fa.d8kGTkzOZH22bXRIRiakqgOPBM4@ifi.uio.no>
2007-12-21 0:44 ` [Fwd: Re: [PATCH 0/5]PCI: x86 MMCONFIG] Robert Hancock
2007-12-21 1:35 ` Tony Camuso
2007-12-21 1:42 ` Tony Camuso
2007-12-21 14:59 ` Bhavana Nagendra
2007-12-21 2:15 ` Robert Hancock
2007-12-21 2:44 ` Tony Camuso
2007-12-21 3:40 ` Loic Prylli
2007-12-21 4:07 ` Tony Camuso
2007-12-21 2:09 ` Tony Camuso [this message]
2007-12-21 14:11 ` Andi Kleen
[not found] ` <fa.pdOcVPk2gFn5iK76ExRH6Ow+NPw@ifi.uio.no>
2007-12-22 16:41 ` Robert Hancock
2007-12-22 16:59 ` [Fwd: Re: [PATCH 4/5]PCI: x86 MMCONFIG] introduce pcibios_fix_bus_scan_quirk() Tony Camuso
[not found] ` <fa.AlLzUeumrcT2SswgOn6MxKfDE0U@ifi.uio.no>
[not found] ` <fa.wIE0QfzMAxr82X049FecszlEnQY@ifi.uio.no>
[not found] ` <fa.2jJbe4cdXLfOVhNWVxdIjsW8GQc@ifi.uio.no>
[not found] ` <fa.JiW7yU0G/EdLOCYcPOacl/XVocc@ifi.uio.no>
[not found] ` <fa.PI93hBriZRT9ggytQ5eY/446Tno@ifi.uio.no>
2007-12-24 17:13 ` [Fwd: Re: [PATCH 0/5]PCI: x86 MMCONFIG] Robert Hancock
2007-12-20 12:28 Tony Camuso
-- strict thread matches above, loose matches on Subject: below --
2007-12-20 12:28 Tony Camuso
2007-12-20 17:22 ` Greg KH
2007-12-20 17:35 ` Matthew Wilcox
2007-12-20 18:04 ` Tony Camuso
2007-12-20 18:16 ` Matthew Wilcox
2007-12-20 18:30 ` Tony Camuso
2007-12-20 18:36 ` Matthew Wilcox
2007-12-20 18:49 ` Loic Prylli
2007-12-20 19:04 ` Tony Camuso
2007-12-20 19:08 ` Matthew Wilcox
2007-12-20 19:50 ` Ivan Kokshaysky
2007-12-20 20:17 ` Tony Camuso
2007-12-20 20:27 ` Tony Camuso
2008-01-08 3:41 ` Tony Camuso
2007-12-20 20:05 ` Loic Prylli
2007-12-20 20:15 ` Matthew Wilcox
2007-12-20 20:56 ` Loic Prylli
2007-12-20 21:00 ` Matthew Wilcox
2007-12-20 21:55 ` Loic Prylli
2007-12-20 19:37 ` Tony Camuso
2007-12-20 20:04 ` Matthew Wilcox
2007-12-20 20:15 ` Tony Camuso
2007-12-23 20:16 ` Loic Prylli
2007-12-23 20:55 ` Matthew Wilcox
2007-12-23 22:40 ` Loic Prylli
2007-12-24 8:09 ` Grant Grundler
2007-12-20 18:25 ` Tony Camuso
2007-12-20 21:57 ` Greg KH
2007-12-20 22:36 ` Tony Camuso
2007-12-20 22:40 ` Greg KH
2007-12-20 23:21 ` Tony Camuso
2007-12-21 2:07 ` Loic Prylli
2007-12-24 8:28 ` Grant Grundler
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=476B2070.7020004@redhat.com \
--to=tcamuso@redhat.com \
--cc=Nagananda.Chumbalkar@hp.com \
--cc=gregkh@suse.de \
--cc=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.