From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Aubin LaBrosse <arl8778@rit.edu>
Cc: Peter Lieverdink <peter@cc.com.au>,
linux-kernel@vger.kernel.org, maverick@eskuel.net
Subject: Re: PCMCIA lockups on HP Pavilion laptop
Date: Sun, 11 Jan 2004 23:11:53 +0000 [thread overview]
Message-ID: <20040111231153.D10920@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1073862011.9478.11.camel@rain.rh.rit.edu>; from arl8778@rit.edu on Sun, Jan 11, 2004 at 06:00:11PM -0500
On Sun, Jan 11, 2004 at 06:00:11PM -0500, Aubin LaBrosse wrote:
> On Sun, 2004-01-11 at 17:34, Peter Lieverdink wrote:
> > http://www.consultmatt.co.uk/nx9005/config.php
> >
> > - Peter.
>
> I'll keep that one in mind as well, thanks Peter. Mathieu's reply
> (earlier in this thread) fixed it for me, i used the config he put in
> his mail. thanks to all of you for your help and insight!
>
> Russell, would it be useful to you if I tracked it down more precisely
> anyway? the config mathieu posted worked for me so i didn't look too
> deep, but if you'd like me to try and narrow it down so that we know
> which io space causes problems on these machines i could do that.
Personally, I don't care very much - it's useful to know the affected
port range vs the machine, so when other people have the same problem
we don't have to re-investigate.
I'd rather there was some way to automatically mark these pesky regions
in the resource manager so we didn't have to do this, but I guess that's
going to be too much.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-01-11 23:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-04 4:53 PCMCIA lockups on HP Pavilion laptop Aubin LaBrosse
2004-01-11 11:49 ` Russell King
2004-01-11 22:34 ` Peter Lieverdink
2004-01-11 23:00 ` Aubin LaBrosse
2004-01-11 23:11 ` Russell King [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-04 8:25 Mathieu LESNIAK
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=20040111231153.D10920@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=arl8778@rit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=maverick@eskuel.net \
--cc=peter@cc.com.au \
/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