From: Jan Mynarik <mynarikj@phoenix.inf.upol.cz>
To: linux-kernel@vger.kernel.org
Subject: Cisco Aironet mini-PCI wireless card (MPI-350) [Was: Re: Intel PRO/Wireless 2100 vs. Broadcom BCM9430x]
Date: 12 Jun 2003 19:20:10 +0200 [thread overview]
Message-ID: <1055438410.930.15.camel@narsil> (raw)
In-Reply-To: <Pine.LNX.4.44.0306120813380.411-100000@twin.uoregon.edu>
Hi,
Cisco's linux support is great until you have IBM's ThinkPad R40. With
this notebook, their newest Linux driver (version 2.0, older ones do not
support my card) module (mpi350.o) can't be inserted to kernel (oops and
module remains 'initializing' forever). Module is compiled successfully
against both 2.4.20 and 2.4.21-rc7 kernels.
I'm just fighting their bureaucracy (in support) and trying to reach
someone who actually wrote the driver (module says Roland Wilcher). I
want to help him with testing and provide him with all possible
information.
My other chance is to get working new driver from
http://airo-linux.sf.net, but there is no activity in last several
weeks.
Jan Mynarik
On Thu, 2003-06-12 at 17:16, Joel Jaeggli wrote:
> most laptop vendors that provide multiple wireless options also support
> the cisco aironet minipci card, you can allways vote with your wallet if
> you think linux support for wireless chipsets is valuable.
>
> joelja
>
> On Thu, 12 Jun 2003, Marc Sowen wrote:
>
> > Hi everybody,
> >
> > I hope this is not too off-topic, but the fact is that neither the Intel
> > PRO/Wireless 2100 (Centrino) chipset nor the Broadcom BCM9430x (e.g.
> > Dell Truemobile 1180/1300/1400) chipset is currently supported in Linux
> > due to FCC regulation problems.
> >
> > Anyhow, I plan to get a new Notebook within the next 2 or 3 weeks and I
> > need to decide, whether to go for the Intel PRO/Wireless 2100 or the
> > Broadcom BCM9430x chipset. I know it's hard to say, but what do you
> > think, which company (Intel or Broadcom) is more likely to release the
> > necessary documents and/or drivers for their chipsets? Both companys
> > seem to ignore all inquiries concerning Linux support at the moment.
> >
> > While we're at it, are there any news from the WLAN front?
> >
> > Thank you!
> >
> > Marc
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
> >
--
Jan Mynarik <mynarikj@phoenix.inf.upol.cz>
next prev parent reply other threads:[~2003-06-12 17:08 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 ` Jan Mynarik [this message]
2003-06-12 17:46 ` Cisco Aironet mini-PCI wireless card (MPI-350) [Was: Re: Intel PRO/Wireless 2100 vs. Broadcom BCM9430x] 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
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=1055438410.930.15.camel@narsil \
--to=mynarikj@phoenix.inf.upol.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox