From: Jochen Friedrich <jochen@scram.de>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
<dahinds@users.sourceforge.net>
Subject: Re: PCI1410 Interrupt Problems
Date: Sun, 3 Aug 2003 23:52:29 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0308032347580.25885-100000@gfrw1044.bocc.de> (raw)
In-Reply-To: <20030803222314.C15221@flint.arm.linux.org.uk>
Hi Russell,
> Can you provide the kernel messages without the hack applied please?
The kernel messages don't differ if the hack is applied or not. The hack
simply configures the PCI1410 to use a particular pin for INTA output.
Without the hack, the counter for IRQ9 in /proc/interrupt simply stays at 0.
Aug 3 14:51:02 rt1-sp kernel: Linux Kernel Card Services 3.1.22
Aug 3 14:51:02 rt1-sp kernel: options: [pci] [cardbus] [pm]
Aug 3 14:51:02 rt1-sp kernel: PCI: Enabling device 02:0a.0 (0000 -> 0002)
Aug 3 14:51:02 rt1-sp kernel: PCI: Found IRQ 9 for device 02:0a.0
Aug 3 14:51:02 rt1-sp kernel: Yenta IRQ list 0000, PCI irq9
Aug 3 14:51:02 rt1-sp kernel: Socket status: 30000010
Aug 3 14:51:03 rt1-sp kernel: cs: IO port probe 0x0c00-0x0cff: clean.
Aug 3 14:51:03 rt1-sp kernel: cs: IO port probe 0x0800-0x08ff: clean.
Aug 3 14:51:03 rt1-sp kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x170-0x177 0x370-0x377 0x3b8-0x3df 0x4d0-0x4d7
Aug 3 14:51:03 rt1-sp kernel: cs: IO port probe 0x0a00-0x0aff: clean.
Aug 3 14:51:03 rt1-sp kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean.
--jochen
next prev parent reply other threads:[~2003-08-03 21:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-03 20:15 PCI1410 Interrupt Problems Jochen Friedrich
2003-08-03 21:23 ` Russell King
2003-08-03 21:52 ` Jochen Friedrich [this message]
2003-08-06 23:09 ` Russell King
2003-08-08 5:40 ` Jochen Friedrich
2003-08-08 8:51 ` Russell King
2003-08-08 17:09 ` Jochen Friedrich
2003-08-11 18:33 ` Jochen Friedrich
2003-08-11 19:00 ` David Hinds
2003-08-12 8:59 ` Russell King
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.44.0308032347580.25885-100000@gfrw1044.bocc.de \
--to=jochen@scram.de \
--cc=dahinds@users.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).