public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: Jochen Friedrich <jochen@scram.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	dahinds@users.sourceforge.net
Subject: Re: PCI1410 Interrupt Problems
Date: Sun, 3 Aug 2003 22:23:15 +0100	[thread overview]
Message-ID: <20030803222314.C15221@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0308032205210.25885-100000@gfrw1044.bocc.de>; from jochen@scram.de on Sun, Aug 03, 2003 at 10:15:09PM +0200

On Sun, Aug 03, 2003 at 10:15:09PM +0200, Jochen Friedrich wrote:
> when using this PCI Cardbus bridge, i got an interrupt assigned to the
> card by the BIOS, but no interrupts were ever delivered, at all. So no
> insert/remove events have been handled and devices couldn't generate
> interrupts, as well:
> 
> 02:0a.0 Class 0607: 104c:ac50 (rev 01)
> 02:0a.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 01)
>         Flags: bus master, medium devsel, latency 168, IRQ 9
>         Memory at 14000000 (32-bit, non-prefetchable) [size=4K]
>         Bus: primary=02, secondary=03, subordinate=06, sec-latency=176
>         Memory window 0: 14400000-147ff000 (prefetchable)
>         Memory window 1: 14800000-14bff000
>         I/O window 0: 00004000-000040ff
>         I/O window 1: 00004400-000044ff
>         16-bit legacy interface ports at 0001
> 
> It looks like the designers of this card "forgot" to put a sane
> configuration of the Multifunction Routing Register (0x8C) in their
> EEPROM. After setting up the INTA output pin of the PCI1410, the device
> started to work like a charm :-)
> 
> This i added to yenta_config_init():
> 
> config_writew(socket, 0x8C, 0x02);
> 
> I'm not sure if this will help with all of these devices of if it even
> makes problems on others. But it might be an idea to add a config option
> for this hack...

Can you provide the kernel messages without the hack applied please?

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html


  reply	other threads:[~2003-08-03 21:24 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 [this message]
2003-08-03 21:52   ` Jochen Friedrich
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=20030803222314.C15221@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=dahinds@users.sourceforge.net \
    --cc=jochen@scram.de \
    --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