From: James Bottomley <James.Bottomley@SteelEye.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: Russell King <rmk+pcmcia@arm.linux.org.uk>,
parisc-linux@lists.parisc-linux.org,
linux-pcmcia@lists.infradead.org,
Kyle McMartin <kyle@parisc-linux.org>
Subject: Re: [parisc-linux] Re: [PATCH] PCMCIA: Disable probing on parisc
Date: Wed, 07 Dec 2005 09:01:10 -0500 [thread overview]
Message-ID: <1133964070.3303.4.camel@mulgrave> (raw)
In-Reply-To: <20051207122129.GA31601@isilmar.linta.de>
On Wed, 2005-12-07 at 13:21 +0100, Dominik Brodowski wrote:
> And only if it succeeds, we read (or write) to such addresses. At least in
> theory. There seems to be a bug -- either in the PARISC setup, or in the
> PCMCIA code -- which triggers this HMAC. Let's find it, as _not_ doing these
> checks seems to be the wrong thing to do. James, could you find out what
> call exactly does this HMAC? Which kernel are you referring to? Also, maybe
> a pcibios_resource_to_bus or pcibios_bus_to_resource translation is missing
> somewhere?
Ah, well, this code has been in parisc for ages ... since I started
using my PA box as a wireless router about two years ago. My
recollection is that it claimed to probe something in low memory as its
first printout. Let me reverse the patch and see what happens now (I
assume the code has been updated a bit since we first had to do this).
It will take a while; I have to bring down my home network to do it and
I won't be back home until Friday.
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-07 14: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 [this message]
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=1133964070.3303.4.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=kyle@parisc-linux.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=linux@dominikbrodowski.net \
--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.