On Thu, Jan 08, 2004 at 08:23:49AM -0800, Leonid Grossman wrote: > > I interpret this to mean: > > Setting the RO bit in the PCI-X Command Register only enables > > the device to choose when to set RO Attribute bit when the device > > generates a PCI-X bus cycle. > > Yes, this is exactly how (at least our 10GbE) PCI-X ASICs work. > If the RO bit is set, the device decides whether the transaction > requires strong ordering, > and sets RO attribute accordingly. Excellent, a card in the wild that actually does this! :) Ok, now I'll take of my sn2 tunnel vision glasses--we don't want another readX variant, but it sounds like we'll need pcix_enable_relaxed() _and_ pci_sync_consistent() to support non-coherent platforms well. How does that sound? Thanks, Jesse - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
References:
- Re: [RFC] Relaxed PIO read vs. DMA write orderingGrant Grundler
- RE: [RFC] Relaxed PIO read vs. DMA write orderingLeonid Grossman
- Prev by Date: Re: [autofs] [RFC] Towards a Modern Autofs
- Next by Date: Re: [PATCH] sysfs sound class patches - [0/2]
- Previous by thread: RE: [RFC] Relaxed PIO read vs. DMA write ordering
- Next by thread: Re: [RFC] Relaxed PIO read vs. DMA write ordering
- Indexes:[Main][Thread]