| To: | Robert Hancock <hancockr@shaw.ca> |
|---|---|
| Subject: | Re: PCI resource unavailable on mips |
| From: | Jon Dufresne <jon.dufresne@infinitevideocorporation.com> |
| Date: | Tue, 18 Dec 2007 13:40:43 -0500 |
| Cc: | linux-kernel@vger.kernel.org, linux-mips <linux-mips@linux-mips.org> |
| In-reply-to: | <4761C26C.3010708@shaw.ca> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <fa.vbvzhsk+kDPCopbmajO8EsxAnKE@ifi.uio.no> <4761C26C.3010708@shaw.ca> |
| Sender: | linux-mips-bounce@linux-mips.org |
> > Bar0:PHYS=e0000000 LEN=04000000 > > Bar1:PHYS=efa00000 LEN=00200000 > > Bar2:PHYS=e8000000 LEN=04000000 > > So, two 64MB BARs and a 2MB one? That is right. > Any PCI resource allocation errors in dmesg during the boot process? > Could be the kernel wasn't able to find a place to map all of the BARs. > I went back and looked at the boot up messages and I found this: PCI: Failed to allocate mem resource #2:4000000@24000000 for 0000:00:0c.0 That is my device. So it does appear that there is an allocation issue. Any idea how to get around this? Thanks, Jon |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: PCI resource unavailable on mips, Jon Dufresne |
|---|---|
| Next by Date: | [MIPS] Build an embedded initramfs into mips kernel, Alon Bar-Lev |
| Previous by Thread: | Re: PCI resource unavailable on mips, Jon Dufresne |
| Next by Thread: | Slow transfer for loopback, Ratin Rahman (mratin) |
| Indexes: | [Date] [Thread] [Top] [All Lists] |