| To: | Stanislaw Skowronek <sskowron@ET.PUT.Poznan.PL> |
|---|---|
| Subject: | Re: pci-ip27 memory ranges |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Sat, 24 Apr 2004 20:21:46 +0200 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <Pine.GSO.4.10.10404241059030.18252-100000@helios.et.put.poznan.pl> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <Pine.GSO.4.10.10404241059030.18252-100000@helios.et.put.poznan.pl> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.4.1i |
On Sat, Apr 24, 2004 at 11:00:44AM +0200, Stanislaw Skowronek wrote: > Why does the pci-ip27 driver register all memory resources (0UL - ~0UL)? I > had to change it to the appropriate Xtalk window to get the kernel to > recognize PCI at all. The IP27 PCI code as it is in CVS is incomplete or even broken - however fixing isn't entirely trivial. The current workaround which I use - and which due to being just an evil hack is not in CVS - to only scan the PCI code. The problem is the firmware does a very simple setup which hurts performance very badly, so eventually Linux will have to do a full PCI configuration for all PCI busses. > Now, the IOC3 makes a kernel panic. Will see... Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Xtalk bridge IRQs, Ralf Baechle |
|---|---|
| Next by Date: | Re: Xtalk bridge IRQs, Stanislaw Skowronek |
| Previous by Thread: | Re: pci-ip27 memory ranges, Christoph Hellwig |
| Next by Thread: | Xtalk bridge IRQs, Stanislaw Skowronek |
| Indexes: | [Date] [Thread] [Top] [All Lists] |