From: David Hinds <dhinds@sonic.net>
To: Thomas Molina <tmolina@cox.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
hermes@gibson.dropbear.id.au, dahinds@users.sourceforge.net,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: 2.5.63 wireless loading problem
Date: Fri, 28 Feb 2003 18:11:58 -0800 [thread overview]
Message-ID: <20030228181158.A1745@sonic.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0302281955380.2070-200000@localhost.localdomain>
On Fri, Feb 28, 2003 at 07:59:47PM -0600, Thomas Molina wrote:
> # CONFIG_ISA is not set
The PCMCIA drivers decide whether or not ISA interrupts are available
based on CONFIG_ISA so you should turn this on.
Perhaps this is a misuse of this configuration option. I'm not sure
what's the right thing to do.
-- Dave
next prev parent reply other threads:[~2003-03-01 2:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-01 1:59 2.5.63 wireless loading problem Thomas Molina
2003-03-01 2:11 ` David Hinds [this message]
2003-03-01 3:03 ` Thomas Molina
2003-03-01 20:34 ` John Weber
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=20030228181158.A1745@sonic.net \
--to=dhinds@sonic.net \
--cc=dahinds@users.sourceforge.net \
--cc=hermes@gibson.dropbear.id.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=tmolina@cox.net \
/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