From: Ed Swierk <eswierk@aristanetworks.com>
To: Yinghai Lu <yinghai@kernel.org>
Cc: jbarnes@virtuousgeek.org, Ingo Molnar <mingo@elte.hu>,
hpa@zytor.com, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: Subject: [PATCH] x86/pci: Detect mmconfig on nVidia MCP55 -v2
Date: Wed, 11 Feb 2009 14:00:35 -0800 [thread overview]
Message-ID: <9ae48b020902111400pa9bc287s12dbbb38bad9866d@mail.gmail.com> (raw)
In-Reply-To: <86802c440902102105w332e496h412733437ca4352d@mail.gmail.com>
On Tue, Feb 10, 2009 at 9:05 PM, Yinghai Lu <yinghai@kernel.org> wrote:
> try to make thing simple.
> for system: with AMD Fam10h, and MCP55 + 2 IO55
> amd fam10h cpu: said it needs [0,0]
> mcp55: said it need [0,255]
> io55 #1: said it need [0x40, 0x40+255], then u8 end_bus_number = 0x3f
> io55 #2: said it need [0x80, 0x80+255], then u8 end_bus_number = 0x7f
> MMIO route in NBs is right.
Oh, I misinterpreted your earlier comment--I thought you were
referring to 0x40, 0x80, 0xc0 as devfns, not bus numbers. The MCP55 is
on device 0 on our board as well.
> but MCFG is right... so just use that.
>
> when acpi=off, if check_and_enable_amd_mconf, it will forcely to make
> amd fam10h cpu: said it needs [0,255] and pci_mmcfg_config_num = 1
> so mcp55 mconf is not used.
OK, I'm just pointing out that the existing mmconfig hostbridge
detection code overrides ACPI MCFG. Past commit comments suggest that
the hostbridge registers are more trustworthy than ACPI on some
boards.
--Ed
next prev parent reply other threads:[~2009-02-11 22:00 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-04 16:39 [PATCH] Detect mmconfig on nVidia MCP55 Ed Swierk
2009-02-04 17:04 ` Ingo Molnar
2009-02-05 17:05 ` Tvrtko Ursulin
2009-02-05 18:00 ` Ingo Molnar
2009-02-06 11:30 ` Tvrtko Ursulin
2009-02-06 15:42 ` Ingo Molnar
2009-02-06 16:10 ` Tvrtko Ursulin
2009-02-09 19:26 ` Ed Swierk
2009-02-09 19:42 ` Yinghai Lu
2009-02-04 17:07 ` Loic Prylli
2009-02-04 17:37 ` Ed Swierk
2009-02-04 20:00 ` Yinghai Lu
2009-02-04 20:12 ` Yinghai Lu
2009-02-04 21:25 ` Ingo Molnar
2009-02-04 23:10 ` Yinghai Lu
2009-02-10 1:59 ` [PATCH] x86/pci: host mmconfig detect clean up v3 Yinghai Lu
2009-02-10 2:00 ` Subject: [PATCH] x86/pci: Detect mmconfig on nVidia MCP55 -v2 Yinghai Lu
2009-02-10 22:57 ` Ed Swierk
2009-02-11 5:05 ` Yinghai Lu
2009-02-11 22:00 ` Ed Swierk [this message]
2009-02-12 5:03 ` Ed Swierk
2009-02-12 5:02 ` [PATCH] x86/pci: host mmconfig detect clean up v3 Ed Swierk
2009-02-05 2:24 ` [PATCH] x86/pci: host mmconfig detect clean up v2 Yinghai Lu
2009-02-05 18:15 ` Ingo Molnar
2009-02-05 18:31 ` Yinghai Lu
2009-02-05 22:04 ` Ed Swierk
2009-02-05 22:36 ` Yinghai Lu
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=9ae48b020902111400pa9bc287s12dbbb38bad9866d@mail.gmail.com \
--to=eswierk@aristanetworks.com \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yinghai@kernel.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;
as well as URLs for NNTP newsgroup(s).