public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@linuxcare.com.au>
To: John Jasen <jjasen@datafoundation.com>,
	Mike Pontillo <mike_p@polaris.wox.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Support for 802.11 cards?
Date: Mon, 29 Jan 2001 13:00:18 +1100	[thread overview]
Message-ID: <20010129130018.B8771@linuxcare.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0101281344040.12805-100000@polaris.wox.org> <Pine.LNX.4.30.0101281704050.2343-100000@flash.datafoundation.com> <20010128182358.F23716@alcove.wittsend.com>
In-Reply-To: <20010128182358.F23716@alcove.wittsend.com>; from mhw@wittsend.com on Sun, Jan 28, 2001 at 06:23:58PM -0500


Hi,
 
> 	Last I knew (straight from the Lucent people), the ISA bridge
> card worked fine and the PCI card did NOT work at all.  I've since
> confirmed that, first hand, myself (I currently have the ISA bridge in
> operation) on the 2.2 kernels.  The ISA bridge also works on the 2.4
> kernels but I have not retested the PCI bridge on 2.4.  The Lucent
> people claim that the Linux pcmcia people are aware of the problem.

I have a PCI -> PCMCIA bridge + lucent wavelan card working fine with the
GPL driver (not the Lucent proprietory one) and 2.4. From memory all I had
to do was stop pcmcia-cs from using the lower io port range (there must
have been conflicts with existing devices).

#include port 0x100-0x4ff, port 0x800-0x8ff, port 0xc00-0xcff
include port 0x800-0x8ff, port 0xc00-0xcff

Anton
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2001-01-29  2:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-26 13:13 Renaming lost+found Rob Kaper
2001-01-26 13:49 ` Richard B. Johnson
2001-01-26 18:19   ` James Lewis Nance
2001-01-26 20:05     ` Rodrigo Barbosa (aka morcego)
2001-01-27 20:43       ` Stephen C. Tweedie
2001-01-28 19:26     ` Chris Mason
2001-01-27 23:14   ` Thunder from the hill
2001-01-28 21:35     ` H. Peter Anvin
2001-01-28 21:41       ` Mo McKinlay
2001-01-28 21:56         ` Support for 802.11 cards? Mike Pontillo
2001-01-28 22:07           ` John Jasen
2001-01-28 23:23             ` Michael H. Warfield
2001-01-29  0:13               ` Joe deBlaquiere
2001-01-29  2:00               ` Anton Blanchard [this message]
2001-01-29 18:18               ` Bryan O'Sullivan
2001-01-30  1:09                 ` Mike Pontillo
2001-01-29  6:41         ` Renaming lost+found Mike Galbraith
2001-01-29  7:17       ` Andreas Dilger
2001-01-31 15:32       ` tytso
2001-01-26 19:24 ` Andreas Dilger
2001-01-26 19:45   ` patrick.mourlhon
     [not found]     ` <200101262005.PAA05246@mah21awu.cas.org>
2001-01-26 20:21       ` patrick.mourlhon

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=20010129130018.B8771@linuxcare.com \
    --to=anton@linuxcare.com.au \
    --cc=jjasen@datafoundation.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike_p@polaris.wox.org \
    /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