public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jochen Friedrich <jochen@scram.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Kyle Moffett <mrmacman_g4@mac.com>, Adrian Bunk <bunk@stusta.de>,
	Lee Revell <rlrevell@joe-job.com>,
	abonilla@linuxwireless.org, "'Andreas Steinmetz'" <ast@domdv.de>,
	"'Arjan van de Ven'" <arjan@infradead.org>,
	"'Denis Vlasenko'" <vda@ilport.com.ua>,
	"'linux-kernel'" <linux-kernel@vger.kernel.org>
Subject: Re: Wireless support
Date: Tue, 09 Aug 2005 18:09:59 +0200	[thread overview]
Message-ID: <42F8D557.9040601@scram.de> (raw)
In-Reply-To: <200508091624.17381.rjw@sisk.pl>

Rafael J. Wysocki wrote:

>On Tuesday, 9 of August 2005 15:52, Kyle Moffett wrote:
>  
>
>>On Aug 9, 2005, at 05:09:55, Jochen Friedrich wrote:
>>    
>>
>>>Third, both ndiswrapper and binary-only drivers only work on one  
>>>platform.
>>>
>>>E.g. broadcom has a binary-only driver for their WLAN card on  
>>>Linux, but
>>>only for mipsel (wrt54g).
>>>
>>>On Alpha or PowerPC, most WLAN equipment doesn't work under Linux,  
>>>at all.
>>>      
>>>
>>Definitely.  I want my Airport Extreme to work!  Many users of the  
>>BCM4301 chip can get it to work (kinda) with Linux via ndiswrapper,
>>but that means they are much less likely to participate in any kind of
>>reverse engineering effort,
>>    
>>
>
>Do you know of anyone actually doing it?
>
>Rafael
>
>  
>

See http://linux-bcom4301.sourceforge.net/

Jochen

  reply	other threads:[~2005-08-09 16:10 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-07 19:22 Wireless support Lee Revell
2005-08-07 19:56 ` Lee Revell
2005-08-08  5:50   ` Martin J. Bligh
2005-08-08 17:57     ` Lee Revell
2005-08-08  0:39 ` Alejandro Bonilla Beeche
2005-08-08  1:20   ` Lee Revell
2005-08-08  1:29     ` Alejandro Bonilla Beeche
2005-08-08  6:31   ` Denis Vlasenko
2005-08-08 17:48     ` Lee Revell
2005-08-08 17:51       ` Arjan van de Ven
2005-08-08 18:13         ` Andreas Steinmetz
2005-08-08 18:19           ` Lee Revell
2005-08-08 18:24             ` Andreas Steinmetz
2005-08-08 18:27               ` Lee Revell
2005-08-08 18:56                 ` Alejandro Bonilla
2005-08-08 19:06                   ` Lee Revell
2005-08-08 19:55                     ` alan
2005-08-08 23:29                     ` Adrian Bunk
2005-08-08 23:43                       ` Alejandro Bonilla Beeche
2005-08-09  9:09                       ` Jochen Friedrich
2005-08-09 13:52                         ` Kyle Moffett
2005-08-09 14:24                           ` Rafael J. Wysocki
2005-08-09 16:09                             ` Jochen Friedrich [this message]
2005-08-12  2:40                           ` Lee Revell
2005-08-12  2:59                             ` roucaries bastien
2005-08-12  3:17                               ` Lee Revell
2005-08-12  4:18                                 ` Kyle Moffett
2005-08-08 19:27                   ` linux-os (Dick Johnson)

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=42F8D557.9040601@scram.de \
    --to=jochen@scram.de \
    --cc=abonilla@linuxwireless.org \
    --cc=arjan@infradead.org \
    --cc=ast@domdv.de \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrmacman_g4@mac.com \
    --cc=rjw@sisk.pl \
    --cc=rlrevell@joe-job.com \
    --cc=vda@ilport.com.ua \
    /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