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 19:45:23 -0500 [thread overview]
Message-ID: <1133829923.3262.1.camel@mulgrave> (raw)
In-Reply-To: <20051205220344.GJ15201@flint.arm.linux.org.uk>
On Mon, 2005-12-05 at 22:03 +0000, Russell King wrote:
> I don't have issue with the I/O side. It's the memory side I'm
> wondering about.
I'm sorry, by I/O reads I mean memory. PA doesn't have any I/O port
cycles (except those which are generated in the busses via mmio
read/write sequences).
> The probing code sets up a mapping to place the CIS at one of the
> regions, and then tries to validate/read the CIS. It then unmaps
> it and maps it into the next place and repeats. Hence, we're
> reading data from the PCMCIA card after setting up various valid
> mappings.
Yes, that's what crashes. Any memory probe to a non-responding address
on PA causes a high priority machine check. This is what trips us up.
We have to explicitly list the responding regions in the config file.
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-06 0:45 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 [this message]
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=1133829923.3262.1.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox