> I'm not sure that can work either. The PCI-X spec is very clear, you > must wait for a non-posted completion if you care about order. Doing a > config read in the driver as a surrogate flush is not good enough in > the general case. Like you say, a pci bridge is free to reorder all > in flight non-posted operations. No, hang on. Nothing can reorder a dependent read to start after a write that it depends on, can it? So a config read of PCI_COMMAND can't start until the completion of a config write of the same register, right? - R. - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
|