Re: [parisc-linux] Untested port of parisc_device to generic device interface

Bjorn Helgaas (bjorn_helgaas@hp.com)
Wed, 13 Nov 2002 09:32:00 -0700


On Wednesday 13 November 2002 12:52 am, Greg KH wrote:
> On Wed, Nov 13, 2002 at 04:46:58PM +0900, Miles Bader wrote:
> > Greg KH <greg@kroah.com> writes:
> > > What is the real reason for needing this, pci_alloc_consistent()? We
> > > have talked about renaming that to dev_alloc_consistent() in the past,
> > > which I think will work for you, right?
> >
> > This this would end up [or have the ability to] invoking a bus-specific
> > routine at some point, right? [so that a truly PCI-specific definition
> > could be still be had]
>
> If that was needed, yes, we should not break that functionality.
>
> Are there any existing archs that need more than just dma_mask moved to
> struct device out of pci_dev? Hm, ppc might need a bit more...

Absolutely. Boxes with multiple IOMMUs (at least ia64, sparc64, parisc)
need to look up the correct IOMMU with which to map the allocated buffer.
Typically this is in the pci_dev sysdata.

Bjorn

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