On Wednesday 24 October 2007, Jeff Garzik wrote:
quoted text
> >> Then a dev_iomap() analogue to pci_iomap() should be pretty 
> >> straightforward to create.
> > 
> > Another minor nit:  addressing the various resource types.
> > The platform bus code has multiple lookup schemes. 
> > 
> > Calls like resource_iomap() might be more flexible, so that
> > lookup schemes can stay flexible.
> 
> I figured that, in the absence of a true, defined BAR concept, the 
> struct device version would simply index into the discussed array of 
> struct resource.  That means any ordering or layout of resources should 
> work, presuming (the usual case) that both driver and platform agree on 
> the resource layout.

So you'd suggest having search utilities (as with platform_bus)
returning resource indices not resources?

Thing is, BARs are usually well defined, but when folk glue
resources together they use whatever order is convenient on
that particular platform.  And different platforms can have
different numbers and types of resources, etc.

- Dave

-
unsubscribe notice
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/