| To: | baitisj@evolution.com |
|---|---|
| Subject: | Re: Au1500 PCI autoconfig issues with multiple PCI devices? |
| From: | Pete Popov <ppopov@mvista.com> |
| Date: | 24 Apr 2003 13:12:11 -0700 |
| Cc: | Jun Sun <jsun@mvista.com>, Linux MIPS mailing list <linux-mips@linux-mips.org> |
| In-reply-to: | <20030424130459.P10148@luca.pas.lab> |
| Organization: | MontaVista Software |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <20030424114832.O10148@luca.pas.lab> <20030424121140.G28275@mvista.com> <20030424130459.P10148@luca.pas.lab> |
| Sender: | linux-mips-bounce@linux-mips.org |
> Here's another question: > What are the goals of the AU1500 PCI auto config? Is it supposed to be a full > implementation, or just enough to work with a PCI card? The reason I ask is > that the DBAu1500 has only one PCI slot, so a simple implementation would > normally suffice. > > Restated: I don't know if the PCI auto config code was designed to work with > all sorts of wacky PCI devices. I don't know if the intention of the code is > to > support the single PCI slot present on the DbAu1500 development board, or if > it > is supposed to be more flexible (and complicated). The MIPS pci auto should work fine with a single PCI bus and it _should_ be a full implementation. The code was ported from PPC some time ago, but sub busses were not tested. Also, if I remember correctly, we simplified a bit the more complex PPC implementation and maybe you're seeing the result of that :) Pete |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Au1500 PCI autoconfig issues with multiple PCI devices?, Jeff Baitis |
|---|---|
| Next by Date: | NCD900 port?, Chip Coldwell |
| Previous by Thread: | Re: Au1500 PCI autoconfig issues with multiple PCI devices?, Jeff Baitis |
| Next by Thread: | Re: Au1500 PCI autoconfig issues with multiple PCI devices?, Jun Sun |
| Indexes: | [Date] [Thread] [Top] [All Lists] |