linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bas Mevissen <ml@basmevissen.nl>
To: Anders Karlsson <anders@trudheim.com>
Cc: Christian Axelsson <smiler@lanil.mine.nu>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: Current status of Intel PRO/Wireless 2100
Date: Tue, 19 Aug 2003 14:43:24 +0200	[thread overview]
Message-ID: <3F421B6C.2050300@basmevissen.nl> (raw)
In-Reply-To: <1060942697.2296.83.camel@tor.trudheim.com>

Anders Karlsson wrote:

> On Fri, 2003-08-15 at 10:10, Christian Axelsson wrote:
> 

  (mini-PCI WLAN cards in notebooks)

> For the time being those mini-PCI cards is dead weight in the laptop I
> am afraid. I hope that either Intel suddenly sees sense (snowflake in
> hell analogy coming on) or some bright spark reverse engineers the card
> and writes an alpha driver that surpasses the functionality of the Intel
> beta drivers they keep under lock and key internally.
> 
> I'll probably locate some Prism CardBus card in the meantime to use.
> 

My dead weight was called Dell TrueMobile 1300 (with BroadCom chipset). 
What I did is buying a NetGear WG311 PCI card (802.11b/g). It contains a 
mini-pci card in a slot unders a metal cover and some small stuff on the 
PCI-shape PCB.

The cover is easy to remove (only 3 pins) and the antenna is not 
soldered, but connected with the same connector as in my notebook. I 
could only connect 1 (main) antenna, but the PCI card has only one 
antenna too. So you only loose antenna diversity.

The NetGear contains an Atheros chipset. There is some open source stuff 
available (URL forgotten) and a driver (mafwifi) with a binary-only 
hardware abstraction. Not really what you want, but at least a start. A 
combination of both may lead to a more desirable result. But for me it 
is fine to use. Only I can not issue bug reports when the driver has 
been loaded since the last boot.

Oh,
#include <stddisclaimer.h>
#include <donttryat.h>
#include <nowarrenty.h>

Regards,

Bas.

BTW. I have a PCI card with Broadcom chipset for sale now :-)




  reply	other threads:[~2003-08-19 12:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-15  9:10 Current status of Intel PRO/Wireless 2100 Christian Axelsson
2003-08-15 10:18 ` Anders Karlsson
2003-08-19 12:43   ` Bas Mevissen [this message]
2003-08-21 17:32     ` Mr. James W. Laferriere
2003-08-22  9:45       ` Bas Mevissen
2003-08-22 13:12         ` Christian Axelsson
2003-08-23 15:44         ` Mr. James W. Laferriere

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=3F421B6C.2050300@basmevissen.nl \
    --to=ml@basmevissen.nl \
    --cc=anders@trudheim.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=smiler@lanil.mine.nu \
    /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;
as well as URLs for NNTP newsgroup(s).