From: Russell King <rmk@arm.linux.org.uk>
To: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: 2.5/2.6 PCMCIA Issues
Date: Wed, 6 Aug 2003 12:23:40 +0100 [thread overview]
Message-ID: <20030806122340.B2094@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20030806103320.A2094@flint.arm.linux.org.uk>; from rmk@arm.linux.org.uk on Wed, Aug 06, 2003 at 10:33:20AM +0100
Ok, more data points.
- Zwane Mwaikambo tried enabling yenta + i82365 + pnp on his machine.
The boot messages for PCMCIA were:
Linux Kernel Card Services 3.1.22
options: [pci] [cardbus] [pm]
...
ti113x: Routing card interrupts to PCI
Yenta IRQ list 0000, PCI irq9
Socket status: 30000006
Intel PCIC probe: not found.
As you can see, the PCIC probe didn't find any PNP devices. No
problems were noticed.
- I've just tried modular PCMCIA, inserting both yenta and i82365 on
an (arm) machine, obviously without PNP here...
Linux Kernel Card Services 3.1.22
options: [pci] [cardbus]
irq 21: nobody cared
Yenta IRQ list 0000, PCI irq21
Socket status: 30000007
irq 22: nobody cared
Yenta IRQ list 0000, PCI irq22
Socket status: 30000811
Intel PCIC probe: <7>PCI: master abort, pc=0xbf020818
PCI: master abort, pc=0xbf020818
PCI: master abort, pc=0xbf020818
not found.
Again, no PNP activity as expected, and no undesirable side effects
caused by inserting and removing PCMCIA cards. (the master aborts
come from attempting to access 0x3e0/1 and having nothing on the PCI
bus to claim it... yes, not even an ISA bridge...)
Could the problem be PNP related? I don't see much material change in
the PNP layer between 2.5.70 and 2.5.71 though.
Can other people try the CONFIG_YENTA=y, CONFIG_I82365=y, CONFIG_PNP=y
and report their results (in particular the dmesg from boot, and whether
the machine locks when they insert a card _after_ boot.)
--
Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux
http://www.arm.linux.org.uk/personal/aboutme.html
next prev parent reply other threads:[~2003-08-06 11:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-04 23:22 2.5/2.6 PCMCIA Issues Misha Nasledov
2003-08-05 13:44 ` Russell King
2003-08-06 4:56 ` Misha Nasledov
2003-08-06 5:59 ` OSDL
2003-08-06 6:42 ` Andrew Morton
2003-08-06 7:11 ` Linus Torvalds
2003-08-06 9:33 ` Russell King
2003-08-06 11:23 ` Russell King [this message]
2003-08-06 15:33 ` Linus Torvalds
2003-08-07 11:29 ` Alan Cox
2003-08-06 6:42 ` Misha Nasledov
2003-08-06 7:06 ` Misha Nasledov
2003-08-06 11:42 ` Adam Belay
2003-08-06 16:26 ` Russell King
2003-08-06 20:34 ` Andrew Morton
2003-08-06 20:53 ` Russell King
[not found] <20031013161010.GH1623@ee.oulu.fi>
2003-10-13 16:15 ` Misha Nasledov
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=20030806122340.B2094@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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.