Messages in this thread | ![/](/images/icornerl.gif) | | Date | Thu, 4 Sep 2003 14:30:30 +0100 | From | Russell King <> | Subject | Re: [PATCH] fix ppc ioremap prototype |
| |
On Thu, Sep 04, 2003 at 10:59:33PM +1000, Paul Mackerras wrote: > > 2. The resource tree won't know about the upper bits or whatever sitting > > in flags, and as such identical addresses on two different buses will > > clash. > > > > Resource start,end needs to be some unique quantity no matter which (PCI) > > bus you are on. > > They are non-overlapping for PCI buses in the same domain. Perhaps > the sensible thing is to have a separate resource tree for each PCI > domain (actually two trees, for I/O and memory space), and have them > contain bus addresses rather than physical addresses. I don't know if > the generic iomem_resource and ioport_resource are still useful if we > do that.
I thought I pointed out that this approach would break request_region and request_mem_region, which are the work-horses of the "this region of space is busy".
Someone would have to (somehow) fix up all drivers which use those functions...
-- Russell King (rmk@arm.linux.org.uk) http://www.arm.linux.org.uk/personal/ Maintainer of: 2.6 ARM Linux - http://www.arm.linux.org.uk/ 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/ 2.6 Serial core
- 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/
| ![\](/images/icornerr.gif) |