public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	jbarnes@virtuousgeek.org,
	Jack Howarth <howarth@bromo.msbb.uc.edu>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86,pci: dmi check for mackpro 2.2 mmconf
Date: Fri, 18 Jul 2008 10:49:45 -0700	[thread overview]
Message-ID: <4880D7B9.8000007@zytor.com> (raw)
In-Reply-To: <86802c440807181047y4ef2f227me72e6474e726596@mail.gmail.com>

Yinghai Lu wrote:
> On Fri, Jul 18, 2008 at 10:44 AM, H. Peter Anvin <hpa@zytor.com> wrote:
>> Yinghai Lu wrote:
>>> change the mconf bus range from [0,0xff] to to [0, 0x3f]
>>> to match range [0xf0000000, 0xf4000000) in e820 tables.
>>>
>>> Signed-off-by: Yinghai Lu <yhlu.kernel@gmail.com>
>>> Tested-by: Jack Howarth <howarth@bromo.msbb.uc.edu>
>> Why is this hard-coded instead of discovered dynamically?
> 
> you mean according to the range reserved in e820 to find out bus range
> that should be used for mmconf?

That would make sense, since you're truncating the mmconf range based on 
some arbitrary limit.  Even better would be to query the hardware 
register which is responsible for the truncation.

	-hpa

  reply	other threads:[~2008-07-18 17:50 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-18 16:41 [PATCH] x86,pci: dmi check for mackpro 2.2 mmconf Yinghai Lu
2008-07-18 16:50 ` Jack Howarth
2008-07-18 17:44 ` H. Peter Anvin
2008-07-18 17:47   ` Yinghai Lu
2008-07-18 17:49     ` H. Peter Anvin [this message]
2008-07-18 17:54       ` Yinghai Lu
2008-07-18 20:19         ` Ingo Molnar
2008-07-18 20:21           ` Yinghai Lu
2008-07-18 20:21 ` Ingo Molnar
2008-07-18 20:26   ` Yinghai Lu
2008-07-19  0:58     ` Jack Howarth
2008-07-19  1:22       ` Yinghai Lu
2008-07-19  3:28         ` Jack Howarth
2008-07-19  3:43           ` Justin Mattock
2008-07-19  4:45           ` Yinghai Lu
2008-07-19  5:12             ` Jack Howarth
2008-07-19  5:28               ` Yinghai Lu
2008-07-19 17:26                 ` Jesse Barnes
2008-07-19 18:19                   ` Jack Howarth
2008-07-19 18:40                   ` Jack Howarth
2008-07-19 19:04                     ` Jesse Barnes
2008-07-19 19:14                       ` Jack Howarth
2008-07-21  6:49                         ` Shaohua Li
2008-07-22 21:15                           ` Jesse Barnes
2008-07-18 20:22 ` [PATCH] x86,pci: detect end_bus_number according to acpi/e820 reserved Yinghai Lu
2008-07-18 20:48   ` Ingo Molnar
2008-07-18 21:48   ` Jack Howarth
2008-07-18 22:27     ` Yinghai Lu
2008-07-18 22:42       ` Jesse Barnes
2008-07-20  6:48         ` Ingo Molnar
2008-07-19  9:16   ` [PATCH] x86,pci: detect end_bus_number according to acpi/e820 reserved - fix Yinghai Lu
2008-07-20  6:44     ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2008-07-22 23:37 [PATCH] x86,pci: dmi check for mackpro 2.2 mmconf Jack Howarth
2008-07-23  0:23 ` Jesse Barnes
2008-07-23  1:00   ` Jack Howarth
2008-07-23  1:32     ` Jesse Barnes
2008-07-23  1:41       ` Jack Howarth
2008-07-23  1:54         ` Shaohua Li

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=4880D7B9.8000007@zytor.com \
    --to=hpa@zytor.com \
    --cc=howarth@bromo.msbb.uc.edu \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=yhlu.kernel@gmail.com \
    /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