[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071213132735.000a2a04@the-village.bc.nu>
Date: Thu, 13 Dec 2007 13:27:35 +0000
From: Alan Cox <alan@...rguk.ukuu.org.uk>
To: benh@...nel.crashing.org
Cc: Ivan Kokshaysky <ink@...assic.park.msu.ru>,
Robert Hancock <hancockr@...w.ca>,
linux-pci@...ey.karlin.mff.cuni.cz,
Linux Kernel list <linux-kernel@...r.kernel.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Possible issue with dangling PCI BARs
> We may be taking a small risk here, but what else do you propose ? The
> problem of dangling BARs is real... One option is for me to address it
> on powerpc and leave x86 alone as it might be more of an issue with
> random crazy embedded firmware for us than it is for x86. As I said, the
> workaround is completely self contained within arch code for now.
I think the cases like the SIL680 are still covered by the comment below
> > Supporting pci_enable_device_io / pci_enable_device_mmio / pci_iomap_io /
> > pci_iomap_mmio seems to cover pretty much all the use cases we have.
> >
> > The users we have right now that are:
> >
> > - pata_cs5520 (can be dealt with easily)
> > - old IDE (with the new resource handling for legacy IDE
> > can use pci_enable_device_io I think, ditto pci/cs5520)
> > - scx200_acb (looks like a simple substitution works)
> > - lpfc pci_enable_device_mmio
> > - qla2xxx pci_enable_device ? (enables IO and MMIO)
>
> Ok.
If we get those in I can fix up libata in no time and sort out the CS5520
devices. Rest is easy providing Bartlomiej can sort out old IDE core.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists