| To: | Michael Stickel <michael.stickel@4g-systems.biz> |
|---|---|
| Subject: | Re: Au1500 PCI-Bus error handler. |
| From: | Ralf Baechle <ralf@linux-mips.org> |
| Date: | Sat, 15 Jan 2005 20:42:19 +0100 |
| Cc: | linux-mips@linux-mips.org |
| In-reply-to: | <200501141819.46601.michael.stickel@4g-systems.biz> |
| Original-recipient: | rfc822;linux-mips@linux-mips.org |
| References: | <200501141819.46601.michael.stickel@4g-systems.biz> |
| Sender: | linux-mips-bounce@linux-mips.org |
| User-agent: | Mutt/1.4.1i |
On Fri, Jan 14, 2005 at 06:19:46PM +0100, Michael Stickel wrote: > I'm currently implementing an Au1500 PCI-Bus error handler, that printk's PCI > Errors. The Au1500 has a PCI error reporting interrupt (AU1500_PCI_ERR_INT = > 22). Has someone in the list some experience with that? And, does someone > know how I can generate a PCI-Bus error? Touching a PCI address that doesn't belong to any device is usually a promising attempt ;-) Ralf |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: crosscompiling and ..., Tom Vrána |
|---|---|
| Next by Date: | Re: compressed kernel image for mips, Ralf Baechle |
| Previous by Thread: | Au1500 PCI-Bus error handler., Michael Stickel |
| Next by Thread: | crosscompiling and, Tom Vrána |
| Indexes: | [Date] [Thread] [Top] [All Lists] |