From: James Bottomley <James.Bottomley@SteelEye.com>
To: Russell King <rmk+pcmcia@arm.linux.org.uk>
Cc: 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: Mon, 05 Dec 2005 16:32:19 -0500 [thread overview]
Message-ID: <1133818340.3395.11.camel@mulgrave> (raw)
In-Reply-To: <20051204103338.GA16791@flint.arm.linux.org.uk>
On Sun, 2005-12-04 at 10:33 +0000, Russell King wrote:
> On Sun, Dec 04, 2005 at 01:04:23AM -0500, Kyle McMartin wrote:
> > PCMCIA port and memory probing is broken on parisc, disabling both
> > allows the PCMCIA subsystem to work on parisc systems.
>
> Do you know why it's broken?
>
> The memory probing works by mapping the CIS into memory and then trying
> to read it. If you're saying it's broken, that implies that we can't
> read the CIS, and therefore we can't use the addresses being probed.
On parisc, any read to a region that doesn't respond HPMCs (crashes) the
box. PA also has separated I/O space, so most random I/O reads are of
non-responding regions.
My solution was simply to force the pcmcia subsystem not to probe and
instead believe the map we passed in from the pcmcia daemon.
James
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next prev parent reply other threads:[~2005-12-05 21:32 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 [this message]
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
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=1133818340.3395.11.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--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.