"J.E.J. Bottomley" wrote:
> We should also allow devices to do all the setup through bus generic
> functions, but leave open the possibility that the driver may (once it knows
> the bus type) obtain the pci_dev (or whatever) from the struct device if it
> really, really has to muck with bus specific registers.
For device discovery and initialization, the generic PCI code has to muck
with PCI specific resources (IO Port, MMIO, and IRQ related stuff primarily).
> As far as the SCSI mid layer goes, all we really need from struct device is
> the dma_mask for setting up the I/O bounce buffers.
> The simplest way to do all of this is probably to add a pointer to the
> dma_mask in struct device and make it point to the same thing in pci_dev.
> If we find we need more than this per device, it could become a pointer
> to a generic dma information structure later on.
uhmm...If we are going to touch dma_mask in pci_dev, then just move it
to struct device and be done with it. Then fixup pci_set_dma_mask()
to do the right thing.
> Since the 53c700 is also used by parisc (including some machines with
> IOMMUs---which, unfortunately, I don't have access to), it probably makes an
> ideal conversion test case.
Duck! (that's going to get fixed it seems) ;^)
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Nov 15 2002 - 22:00:30 EST