| To: | Sergei Shtylyov <sshtylyov@ru.mvista.com> |
|---|---|
| Subject: | Re: Linux MIPS PCI resource sanity check |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Tue, 19 Feb 2008 15:30:08 +0000 |
| Cc: | Michael Buesch <mb@bu3sch.de>, linux-mips@linux-mips.org |
| In-reply-to: | <47B6BFD4.5050404@ru.mvista.com> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <200802161139.10791.mb@bu3sch.de> <47B6BFD4.5050404@ru.mvista.com> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.5.17 (2007-11-01) |
On Sat, Feb 16, 2008 at 01:49:56PM +0300, Sergei Shtylyov wrote: > It makes sure that a PCI resource is allocated (base of 0 means that it's > unallocated due to previously detected resource conlict (or some other > reason). > >> It triggers for me on a BCM4318 device which is behind a BCM4710 PCI bridge. >> r->start is 0 and r->end is 0x1FFF when this triggers. >> If I simply comment out that check the device is detected correctly >> and seems to initialize just fine. > > No, that failnig resource should be relocated. The resources were assigned during the PCI bus scan so at least with the current implementation it's too late to reassign resources. I get the feeling this is an indication of a problem elsewhere. Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [2.6 patch] mips: finish the Qemu platform removal, Ralf Baechle |
|---|---|
| Next by Date: | Re: Linux MIPS PCI resource sanity check, Ralf Baechle |
| Previous by Thread: | Re: Linux MIPS PCI resource sanity check, Sergei Shtylyov |
| Next by Thread: | Re: Linux MIPS PCI resource sanity check, Ralf Baechle |
| Indexes: | [Date] [Thread] [Top] [All Lists] |