From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: Greg KH <greg@kroah.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Chris Dearman <chris@mips.com>,
"Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: [PATCH] Don't touch BARs of host bridges
Date: Fri, 10 Dec 2004 15:46:38 +1100 [thread overview]
Message-ID: <1102653999.22763.22.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.61.0412092349560.6535@perivale.mips.com>
On Fri, 2004-12-10 at 00:20 +0000, Maciej W. Rozycki wrote:
> Hello,
>
> BARs of host bridges often have special meaning and AFAIK are best left
> to be setup by the firmware or system-specific startup code and kept
> intact by the generic resource handler. For example a couple of host
> bridges used for MIPS processors interpret BARs as target-mode decoders
> for accessing host memory by PCI masters (which is quite reasonable).
Not very reasonable in fact imho but that happens on some embedded PPCs
was well :) So I agree, that would be useful to skip them. I'm not sure
about PCI_CLASS_NOT_DEFINED tho ...
next prev parent reply other threads:[~2004-12-10 4:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-10 0:20 [PATCH] Don't touch BARs of host bridges Maciej W. Rozycki
2004-12-10 4:46 ` Benjamin Herrenschmidt [this message]
2004-12-10 13:11 ` Maciej W. Rozycki
2004-12-10 21:25 ` Benjamin Herrenschmidt
2004-12-13 2:46 ` Maciej W. Rozycki
2004-12-17 21:46 ` Greg KH
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=1102653999.22763.22.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=chris@mips.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=macro@mips.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 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.