From: James Bottomley <James.Bottomley@SteelEye.com>
To: Grant Grundler <grundler@parisc-linux.org>
Cc: Helge Deller <deller@gmx.de>,
Russell King <rmk+pcmcia@arm.linux.org.uk>,
linux-pcmcia@lists.infradead.org,
parisc-linux@lists.parisc-linux.org,
Kyle McMartin <kyle@parisc-linux.org>
Subject: Re: [parisc-linux] Re: [PATCH] PCMCIA: Disable probing on parisc
Date: Sun, 11 Dec 2005 12:01:02 -0600 [thread overview]
Message-ID: <1134324062.3367.9.camel@mulgrave> (raw)
In-Reply-To: <20051211175004.GA22449@colo.lackof.org>
On Sun, 2005-12-11 at 10:50 -0700, Grant Grundler wrote:
> On Sun, Dec 11, 2005 at 09:14:33AM -0600, James Bottomley wrote:
> > The question is would it without the pcmcia hack?
>
> *nod*. If PCMCIA code is accessing IO Port space looking for legacy
> ISA devices, then a parisc box will definitely HPMC.
Well, I pulled out the mem probe and left in the PCMCIA_PROBE config
setting based on !PARISC.
Everything seems to work. Here's the relevant dmesg output
Yenta: CardBus bridge found at 0000:00:02.0 [0000:0000]
PCI: Bus 1, cardbus bridge: 0000:00:02.0
IO window: 00000400-000005ff
IO window: 00000800-000009ff
PREFETCH window: f0c00000-f0ffffff
MEM window: f0900000-f09fffff
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:00:02.0, mfunc 0x00000000, devctl 0x66
Yenta TI: socket 0000:00:02.0 probing PCI interrupt failed, trying to
fix
Yenta TI: socket 0000:00:02.0 falling back to parallel PCI interrupts
Yenta TI: socket 0000:00:02.0 parallel PCI interrupts ok
Yenta: ISA IRQ mask 0x0000, PCI irq 23
Socket status: 30000010
pcmcia: parent PCI bridge I/O window: 0x0 - 0xffff
pcmcia: parent PCI bridge Memory window: 0xf0800000 - 0xf0ffffff
pccard: PCMCIA card inserted into slot 0
[...]
cs: memory probe 0xf0800000-0xf0ffffff: excluding 0xf0800000-0xf087ffff
0xf0900000-0xf09fffff 0xf0c00000-0xf0ffffff
pcmcia: registering new device pcmcia0.0
pcmcia: Detected deprecated PCMCIA ioctl usage.
pcmcia: This interface will soon be removed from the kernel; please
expect breakage unless you upgrade to new tools.
pcmcia: see
http://www.kernel.org/pub/linux/utils/kernel/pcmcia/pcmcia.html for
details.
orinoco 0.15rc3 (David Gibson <hermes@gibson.dropbear.id.au>, Pavel
Roskin <proski@gnu.org>, et al)
As you can see, we do get the cis memory probe occuring within the
correct boundaries now.
Helge, I think the next test is over to you, could you see how CVS tree
head fares on your tadpole?
Thanks,
James
next prev parent reply other threads:[~2005-12-11 18:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-04 6:04 [parisc-linux] [PATCH] PCMCIA: Disable probing on parisc Kyle McMartin
2005-12-04 10:33 ` [parisc-linux] " Russell King
2005-12-04 17:52 ` Kyle McMartin
2005-12-05 21:32 ` James Bottomley
2005-12-05 22:03 ` Russell King
2005-12-06 0:45 ` James Bottomley
2005-12-06 9:36 ` Russell King
2005-12-06 13:36 ` James Bottomley
2005-12-07 12:21 ` Dominik Brodowski
2005-12-07 14:01 ` James Bottomley
2005-12-11 6:50 ` Grant Grundler
2005-12-11 15:14 ` James Bottomley
2005-12-11 17:50 ` Grant Grundler
2005-12-11 18:01 ` James Bottomley [this message]
2005-12-11 18:55 ` Helge Deller
2005-12-11 19:09 ` Matthew Wilcox
2005-12-11 19:49 ` Dominik Brodowski
2005-12-11 20:37 ` James Bottomley
2005-12-11 22:35 ` Helge Deller
2005-12-12 7:30 ` Grant Grundler
2005-12-12 14:45 ` James Bottomley
2005-12-12 21:17 ` Helge Deller
2005-12-13 22:28 ` Grant Grundler
2005-12-11 19:48 ` Dominik Brodowski
2005-12-11 20:23 ` James Bottomley
2005-12-06 8:14 ` Grant Grundler
2005-12-06 9:49 ` Russell King
2005-12-06 16:46 ` Grant Grundler
2005-12-11 7:41 ` Grant Grundler
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=1134324062.3367.9.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=deller@gmx.de \
--cc=grundler@parisc-linux.org \
--cc=kyle@parisc-linux.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=rmk+pcmcia@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 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.