Messages in this thread | | | Date | Fri, 17 Dec 2004 13:46:46 -0800 | From | Greg KH <> | Subject | Re: [PATCH] Don't touch BARs of host bridges |
| |
On Fri, Dec 10, 2004 at 12:20:40AM +0000, Maciej W. Rozycki wrote: > Hello, > > BARs of host bridges often have special meaning and AFAIK are best left > to be setup by the firmware or system-specific startup code and kept > intact by the generic resource handler. For example a couple of host > bridges used for MIPS processors interpret BARs as target-mode decoders > for accessing host memory by PCI masters (which is quite reasonable). > For them it's desirable to keep their decoded address range overlapping > with the host RAM for simplicity if nothing else (I can imagine running > out of address space with lots of memory and 32-bit PCI with no DAC > support in the participating devices). > > This is already the case with the i386 and ppc platform-specific PCI > resource allocators. Please consider the following change for the generic > allocator. Currently we have a pile of hacks implemented for host bridges > to be left untouched and I'd be pleased to remove them.
I've applied this to my trees, and it will show up in the next -mm release, and then on to Linus's tree after 2.6.10 is out.
Oh, and next time, I need a "Signed-off-by:" line as per Documentation/SubmittingPatches.
thanks,
greg k-h - 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/
| |