From: Marcel Holtmann <marcel@holtmann.org>
To: daniel.ritz@gmx.ch
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: No interrupts for PCMCIA cards
Date: Mon, 05 Apr 2004 01:07:04 +0200 [thread overview]
Message-ID: <1081120023.4635.3.camel@pegasus> (raw)
In-Reply-To: <200404042338.47368.daniel.ritz@gmx.ch>
Hi Daniel,
> you can try my TI interrupt routing patch:
> http://ritz.dnsalias.org/linux/pcmcia-ti-routing-9.patch
> also included in 2.6.5-rc3-mm1 and higher:
> http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.5-rc3/2.6.5-rc3-mm4/broken-out/yenta-TI-irq-routing-fix.patch
>
> also the dmesg output with my patch applied would be nice to see...
thanks for the fast reply. This patch brings everything back in shape
and here is the Yenta part from dmesg:
Linux Kernel Card Services
options: [pci] [cardbus] [pm]
PCI: Enabling device 0000:02:0e.0 (0000 -> 0002)
Yenta: CardBus bridge found at 0000:02:0e.0 [0000:0000]
Yenta: Enabling burst memory read transactions
Yenta: Using CSCINT to route CSC interrupts to PCI
Yenta: Routing CardBus interrupts to PCI
Yenta TI: socket 0000:02:0e.0, mfunc 0x00000000, devctl 0x66
Yenta TI: socket 0000:02:0e.0 probing PCI interrupt failed, trying to fix
Yenta TI: socket 0000:02:0e.0 falling back to parallel PCI interrupts
Yenta TI: socket 0000:02:0e.0 parallel PCI interrupts ok
Yenta: ISA IRQ mask 0x0000, PCI irq 18
Socket status: 30000047
NET: Registered protocol family 23
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0800-0x08ff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f 0x3c0-0x3df 0x4d0-0x4d7
cs: IO port probe 0x0a00-0x0aff: clean.
Regards
Marcel
next prev parent reply other threads:[~2004-04-04 23:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-04 21:38 No interrupts for PCMCIA cards Daniel Ritz
2004-04-04 23:07 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-04-04 19:51 Marcel Holtmann
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=1081120023.4635.3.camel@pegasus \
--to=marcel@holtmann.org \
--cc=daniel.ritz@gmx.ch \
--cc=linux-kernel@vger.kernel.org \
/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