From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Anders Karlsson <anders@trudheim.com>
Cc: Joel Jaeggli <joelja@darkwing.uoregon.edu>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Intel PRO/Wireless 2100 vs. Broadcom BCM9430x
Date: 12 Jun 2003 14:17:55 -0700 [thread overview]
Message-ID: <1055452675.13998.2.camel@ixodes.goop.org> (raw)
In-Reply-To: <1055450268.3989.27.camel@tor.trudheim.com>
On Thu, 2003-06-12 at 13:37, Anders Karlsson wrote:
> And that is if your laptop will allow such a card to be plugged in and
> used of course. Thinkpads with the tcpa chip in them might not allow
> such a card,
Nothing to do with TCPA: my laptop doesn't have one, and it objects to
"foreign" wireless cards. Plain old BIOS is enough.
Fortunately IBM support the Cisco Airo 350 mini-pci card, and supply a
(GPLed) driver. It isn't the greatest driver (no 2.5 port, seems flakey
when doing anything with the admin tool, no wireless extension support),
but it works enough to make wireless useful.
J
next prev parent reply other threads:[~2003-06-12 21:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-12 15:15 Intel PRO/Wireless 2100 vs. Broadcom BCM9430x Marc Sowen
2003-06-12 15:16 ` Joel Jaeggli
2003-06-12 17:20 ` Cisco Aironet mini-PCI wireless card (MPI-350) [Was: Re: Intel PRO/Wireless 2100 vs. Broadcom BCM9430x] Jan Mynarik
2003-06-12 17:46 ` Jeremy Fitzhardinge
2003-06-13 10:58 ` Jan Mynarik
2003-06-13 16:29 ` Jeremy Fitzhardinge
2003-06-12 20:37 ` Intel PRO/Wireless 2100 vs. Broadcom BCM9430x Anders Karlsson
2003-06-12 21:17 ` Jeremy Fitzhardinge [this message]
2003-06-12 21:52 ` Anders Karlsson
2003-06-12 21:57 ` Jeremy Fitzhardinge
2003-06-13 3:56 ` Joel Jaeggli
2003-06-12 17:08 ` Davide Libenzi
2003-06-12 17:22 ` Disconnect
2003-06-12 18:07 ` Martin List-Petersen
2003-06-12 20:35 ` Anders Karlsson
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=1055452675.13998.2.camel@ixodes.goop.org \
--to=jeremy@goop.org \
--cc=anders@trudheim.com \
--cc=joelja@darkwing.uoregon.edu \
--cc=linux-kernel@vger.kernel.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 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.