From: Russell King <rmk@arm.linux.org.uk>
To: kernel <linux-kernel@vger.kernel.org>
Subject: Re: Same problem with pcmcia in 2.4.22 as in 2.6.0-test4
Date: Thu, 4 Sep 2003 18:03:51 +0100 [thread overview]
Message-ID: <20030904180351.G8414@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030904123258.GA7674@iain-vaio-fx405>; from ibroadfo@cis.strath.ac.uk on Thu, Sep 04, 2003 at 01:32:58PM +0100
On Thu, Sep 04, 2003 at 01:32:58PM +0100, iain d broadfoot wrote:
> * Russell King (rmk@arm.linux.org.uk) wrote:
> > Could you try the updated debugging patch there please? It should
> > print something extra no matter what.
> >
> > Could you also provide the kernel messages which include the
> > initialisation of your PCMCIA or CardBus bridge please?
>
> are these the right lines?
>
> =======================================================================
> cs: IO port probe 0x0c00-0x0cff: clean.
> cs: IO port probe 0x0800-0x08ff: clean.
> cs: IO port probe 0x0100-0x04ff: excluding 0x3c0-0x3df 0x4d0-0x4d7
> cs: IO port probe 0x0a00-0x0aff: clean.
> cs: memory probe 0xa0000000-0xa0ffffff: clean.
> cs: request irq: pci irq 11 mask 0090
> orinoco_cs: RequestIRQ: Resource in use
> =======================================================================
>
> that's from my boot sequence - I pulled and inserted the card and got
> the last two lines again.
Ok, I'm mostly happy that it isn't a generic PCMCIA bug as such now -
it seems that orinoco_cs may be passing a mask which doesn't include
any reasonable IRQs, or the two available IRQs (7 and 4) are already
in use by other devices.
Hmm, I wonder if we could fall back to the PCI IRQ when this occurs.
Unfortunately I can't look into the issue as deeply as I'd like at
present, so I'll create a "wouldn't it be nice if" (WIBNI) list of
things to do on pcmcia.arm.linux.org.uk.
--
Russell King (rmk@arm.linux.org.uk) http://www.arm.linux.org.uk/personal/
Maintainer of:
2.6 ARM Linux - http://www.arm.linux.org.uk/
2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2003-09-04 17:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-26 22:25 problems with sound and mouse with 2.6.0-test4-mm1 Max Valdez
2003-08-23 11:24 ` 2.6.0t4 - no pcmcia iain d broadfoot
2003-08-23 11:40 ` Russell King
2003-08-23 11:51 ` iain d broadfoot
2003-08-26 22:34 ` Same problem with pcmcia in 2.4.22 as in 2.6.0-test4 iain d broadfoot
2003-08-31 12:10 ` iain d broadfoot
2003-08-31 12:38 ` Russell King
2003-09-02 20:30 ` iain d broadfoot
2003-09-02 21:44 ` Russell King
2003-09-04 12:32 ` iain d broadfoot
2003-09-04 17:03 ` Russell King [this message]
2003-09-05 12:35 ` iain d broadfoot
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=20030904180351.G8414@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.