Re: [patch 2.6.14-rc1] pci: only call pci_restore_bars at boot

On Wed, Sep 14, 2005 at 09:26:50AM -0700, David S. Miller wrote:
> Why in the world can a PCI device not handle it's BARs being
> rewritten, especially if we're just rewriting the same exact
> values it had when we probed it beforehand?

Definitely. I wonder whether pci_resource_to_bus() works
correctly on this platform.

Ivan.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [patch 2.6.14-rc1] pci: only call pci_restore_bars at boot
    • From: "John W. Linville" <[email protected]>
  • Re: [patch 2.6.14-rc1] pci: only call pci_restore_bars at boot
    • From: Jeff Garzik <[email protected]>
  • Re: [patch 2.6.14-rc1] pci: only call pci_restore_bars at boot
    • From: "David S. Miller" <[email protected]>

• Prev by Date: [patch] hdaps driver update, updated.
• Next by Date: Re: USB digital camera erroneously says "no medium found"
• Previous by thread: Re: [patch 2.6.14-rc1] pci: only call pci_restore_bars at boot
• Next by thread: Re: [patch 2.6.12 (repost w/ corrected subject)] pci: restore BAR values in pci_enable_device_bars
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]