On Thu, 25 Jan 2007, Linus Torvalds wrote: > > Have you noticed that the resource-allocation code _already_ never returns > zero on sparc64? Btw, that was a rhetorical question, and I'm not actually sure what the heck sparc64 will _really_ do ;) I picked sparc64 as an example, because I _think_ that sparc64 actually is an example of an architecture that sets up a separate root resource for each PCI domain, and they are actually set up so that the ioport regions are literally offset to match the hardware bases (and there are several different kinds of PCI domain controllers that sparc supports, so those bases will depend on that too). So on sparc64, "ioport_resource" really is just a container for the actual per-domain resource buckets that the hardware (within that domain) will then do the resource allocation from. Afaik. But you should actaully verify that with somebody like Davem if you _really_ care. I cc'd him in case he wants to pipe up and perhaps prove me wrong. Linus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- [PATCH] libata-sff: Don't call bmdma_stop on non DMA capable controllers
- From: Alan <[email protected]>
- Re: [PATCH] libata-sff: Don't call bmdma_stop on non DMA capable controllers
- From: David Woodhouse <[email protected]>
- Re: [PATCH] libata-sff: Don't call bmdma_stop on non DMA capable controllers
- From: Alan <[email protected]>
- Re: [PATCH] libata-sff: Don't call bmdma_stop on non DMA capable controllers
- From: Linus Torvalds <[email protected]>
- Re: [PATCH] libata-sff: Don't call bmdma_stop on non DMA capable controllers
- From: David Woodhouse <[email protected]>
- Re: [PATCH] libata-sff: Don't call bmdma_stop on non DMA capable controllers
- From: Linus Torvalds <[email protected]>
- Re: [PATCH] libata-sff: Don't call bmdma_stop on non DMA capable controllers
- From: David Woodhouse <[email protected]>
- Re: [PATCH] libata-sff: Don't call bmdma_stop on non DMA capable controllers
- From: Linus Torvalds <[email protected]>
- Re: [PATCH] libata-sff: Don't call bmdma_stop on non DMA capable controllers
- From: David Woodhouse <[email protected]>
- Re: [PATCH] libata-sff: Don't call bmdma_stop on non DMA capable controllers
- From: Linus Torvalds <[email protected]>
- Re: [PATCH] libata-sff: Don't call bmdma_stop on non DMA capable controllers
- From: David Woodhouse <[email protected]>
- Re: [PATCH] libata-sff: Don't call bmdma_stop on non DMA capable controllers
- From: Linus Torvalds <[email protected]>
- Re: [PATCH] libata-sff: Don't call bmdma_stop on non DMA capable controllers
- From: David Woodhouse <[email protected]>
- Re: [PATCH] libata-sff: Don't call bmdma_stop on non DMA capable controllers
- From: Linus Torvalds <[email protected]>
- [PATCH] libata-sff: Don't call bmdma_stop on non DMA capable controllers
- Prev by Date: Re: [Ksummit-2006-discuss] 2007 Linux Kernel Summit
- Next by Date: Re: SATA ahci Bug in 2.6.19.x
- Previous by thread: Re: [PATCH] libata-sff: Don't call bmdma_stop on non DMA capable controllers
- Next by thread: Re: [PATCH] libata-sff: Don't call bmdma_stop on non DMA capable controllers
- Index(es):