From: Greg KH <gregkh@suse.de>
To: "David S. Miller" <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, ralf@linux-mips.org,
linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: PCI probe leaves master abort disabled in PCI_BRIDGE_CONTROL
Date: Mon, 13 Feb 2006 21:17:00 -0800 [thread overview]
Message-ID: <20060214051700.GA28721@suse.de> (raw)
In-Reply-To: <20060213.171321.126221906.davem@davemloft.net>
On Mon, Feb 13, 2006 at 05:13:21PM -0800, David S. Miller wrote:
>
> In drivers/pci/probe.c:pci_scan_bridge(), if this is not the first
> pass (pass != 0) we don't restore the PCI_BRIDGE_CONTROL_REGISTER and
> thus leave PCI_BRIDGE_CTL_MASTER_ABORT off:
>
> int __devinit pci_scan_bridge(struct pci_bus *bus, struct pci_dev * dev, int max, int pass)
> {
> ...
> /* Disable MasterAbortMode during probing to avoid reporting
> of bus errors (in some architectures) */
> pci_read_config_word(dev, PCI_BRIDGE_CONTROL, &bctl);
> pci_write_config_word(dev, PCI_BRIDGE_CONTROL,
> bctl & ~PCI_BRIDGE_CTL_MASTER_ABORT);
> ...
> if ((buses & 0xffff00) && !pcibios_assign_all_busses() && !is_cardbus) {
> unsigned int cmax, busnr;
> /*
> * Bus already configured by firmware, process it in the first
> * pass and just note the configuration.
> */
> if (pass)
> return max;
> ...
> }
>
> pci_write_config_word(dev, PCI_BRIDGE_CONTROL, bctl);
> ...
>
> This doesn't seem intentional.
No it doesn't. Ralf added that code, way back in 2.6.2-rc2, with a
patch description of "[PATCH] PCI: fix probing for some mips systems"
David, does this break some stuff on your boxes?
Ralf, any thoughts? It was way back in January of 2004 that this change
went in.
thanks,
greg k-h
next prev parent reply other threads:[~2006-02-14 5:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-14 1:13 PCI probe leaves master abort disabled in PCI_BRIDGE_CONTROL David S. Miller
2006-02-14 5:17 ` Greg KH [this message]
2006-02-14 16:23 ` Ralf Baechle
2006-02-14 21:58 ` David S. Miller
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=20060214051700.GA28721@suse.de \
--to=gregkh@suse.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=ralf@linux-mips.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