public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Tim Hockin <thockin@sun.com>
Cc: mj@ucw.cz, alan@redhat.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH]  PCI probing status cleanup
Date: Tue, 10 Jul 2001 08:37:09 -0400	[thread overview]
Message-ID: <3B4AF6F5.D7F41BDB@mandrakesoft.com> (raw)
In-Reply-To: <3B4AA705.29150671@sun.com>

Tim Hockin wrote:
>         /* some broken boards return 0 or ~0 if a slot is empty: */
> -       if (l == 0xffffffff || l == 0x00000000 || l == 0x0000ffff || l == 0xffff0000)
> +       if (l == 0xffffffff || l == 0x00000000
> +        || l == 0x0000ffff || l == 0xffff0000) {
> +               /*
> +                * host/pci and pci/pci bridges will set Received Master Abort
> +                * (bit 13) on failed configuration access (happens when
> +                * searching for devices).  To be safe, clear the status
> +                * register.
> +                */
> +               unsigned short st;
> +               pci_read_config_word(temp, PCI_STATUS, &st);
> +               pci_write_config_word(temp, PCI_STATUS, st);
>                 return NULL;
> +       }

ok, though I wonder if we shouldn't just clear status for all PCI
devices on boot for paranoia's sake.

-- 
Jeff Garzik      | A recent study has shown that too much soup
Building 1024    | can cause malaise in laboratory mice.
MandrakeSoft     |

      reply	other threads:[~2001-07-10 12:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-10  6:56 [PATCH] PCI probing status cleanup Tim Hockin
2001-07-10 12:37 ` Jeff Garzik [this message]

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=3B4AF6F5.D7F41BDB@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=alan@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mj@ucw.cz \
    --cc=thockin@sun.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