public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Disconnect <lkml@sigkill.net>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Intel PRO/Wireless 2100 vs. Broadcom BCM9430x
Date: 12 Jun 2003 13:22:01 -0400	[thread overview]
Message-ID: <1055438520.11780.36.camel@slappy> (raw)
In-Reply-To: <Pine.LNX.4.55.0306120957260.3626@bigblue.dev.mcafeelabs.com>

On Thu, 2003-06-12 at 13:08, Davide Libenzi wrote:
> 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.
> 
> I used to win the "Dumb context 2003" by buying a laptop w/out checking
> the hw compatibility list. It was first sight love :) Now after a series
> of custom patches (SiS chipset, pcmcia irq selection, local apic,...)
> everything is working fine but the Broadcom integrated WLAN. I suggest you
> to go with a machine w/out the integrated WLAN and then buy a supported
> pcmcia card (orinoco prismII works great on my machine). To understand who
> between Intel and Broadcom will first release specs, take a look at their
> web sites for documentation/specs. The answer will become pretty easy.

Find out which one is in that linksys possible-gpl-violation and use
that one.  (I think its broadcom.) 

FWIW I got my laptop with the broadcom (dell truemobile) intentionally,
as it is useful under XP and might eventually work under Linux.  (Then I
bought the older truemobile, the 1150 I think, for $80 or so. Swapped
right in, leaving the pcmcia slot for my ipaq's hdd, etc.  Even the
Fn-wireless button correctly turns the radio on/off, although Linux has
no way to detect it except loss of signal.)

-- 
Disconnect <lkml@sigkill.net>


  reply	other threads:[~2003-06-12 17:09 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
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 [this message]
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=1055438520.11780.36.camel@slappy \
    --to=lkml@sigkill.net \
    --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